There were 32 Heroku outages since January 2025 which are summarized below, including incident details, duration, and resolution information.
Heroku not working for you?
Heroku not working for you?
Minor
: Heroku App and Data services degraded briefly
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour and 20 minutes)
An outage affected Heroku Apps and Data components, causing degraded performance for a subset of users. The incident began at when Heroku reported a service disruption and moved Apps and Data to a degraded state; engineers were investigating. The issue persisted for about 1 hour 20 minutes and was resolved by when the status returned to up. The provider issued 2 official status updates during the incident.
Minor
: Heroku Tools feature disruption briefly degrades APIs and dashboards
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour and 15 minutes)
The Heroku Tools component experienced a feature disruption that caused API access and dashboard/deployments issues for users. The outage lasted about 1 hour and 15 minutes, beginning when the status page moved from up to warn at and ending when it returned to up at . The incident was publicly described as a feature disruption affecting the Tools component during investigations by Heroku engineers.
Heroku published two status updates during the incident to communicate investigation progress and restoration. User reports came from multiple regions, including Brazil, Kenya, Pakistan, Poland, France, and the United States, indicating broadly distributed impact on APIs, deployments, and dashboard access. The Tools component subsequently returned to normal operation as the issue was resolved.
An outage began on and affected a broad set of Salesforce cloud services, including Heroku, Commerce Cloud, Core services, Hyperforce, MuleSoft, Marketing Cloud Engagement, Marketing Cloud Account Engagement, Slack, and Tableau. Users experienced outages and degraded performance across apps and data workloads, with three components—Tools, Data, and Apps—impacted. Data and Apps degraded by while Tools recovered, and full recovery was achieved by .
The issue was traced to a disruption triggered by a third-party vendor; the Salesforce Technology team notified the vendor and coordinated a resolution. The Salesforce status page provided updates as the situation evolved, issuing three official updates during the incident and directing users to the Salesforce Trust page for the latest impact and status.
The disruption represented a broad, multi-service outage across multiple Salesforce cloud offerings rather than a localized regional fault, underscoring the interconnected nature of the platform. The incident culminated in all affected components returning to normal by the end of the event.
Major
: Heroku runtime outage impacts apps in US and EU
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour and 5 minutes)
Heroku's runtime experienced a regional outage that impacted apps in the United States and Europe due to elevated H99 platform errors. Users attempting to run or deploy apps could have faced failures or degraded performance during the incident. The outage began at and persisted until , lasting about 3 hours with US and EU regions affected. The incident affected the Apps component and disrupted typical app operation.
Major
: Heroku Apps outage due to elevated H99 errors in US & EU
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(50 minutes)
Heroku Apps experienced an outage affecting the runtime in US and EU regions due to elevated H99 platform errors. Users were unable to deploy or run applications during the incident. The outage began at and was resolved by , lasting roughly 1 hour and 21 minutes. The issue was acknowledged on Heroku's status page with an update that engineers were investigating and working to resolve the elevated H99 errors, and the incident included two official status updates before resolution.
Minor
: Heroku AI gpt-oss-120b responses degraded in US region
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(9 hours and 20 minutes)
The Heroku AI service experienced degraded API responses for the gpt-oss-120b model in the US region, affecting applications relying on that model with slower or failed AI queries. The outage began at and was resolved by , lasting about 9 hours and 20 minutes. The Data component of Heroku's AI stack was the primary surface of impact.
During the incident, Heroku issued two status updates to communicate progress and resolution. The issue was regional to the US; no wider global impact was reported. Service for the gpt-oss-120b model was restored by .
Minor
: Heroku DNS issue delays provisioning for new apps and domains
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(19 hours and 10 minutes)
Heroku reported an incident affecting DNS for new apps and domains, making DNS records for new apps and domains unreachable and delaying provisioning. This disruption impacted developers trying to create new Heroku apps or configure custom domains, tied to the Apps component on Heroku's status page.
The outage began on and was resolved by , lasting about 19 hours and 10 minutes. Heroku published two status updates during the event, noting an upstream DNS provider as the cause. The Apps component transitioned from warn back to up with the final update, restoring normal operation.
The Heroku platform experienced degraded app performance due to increased dyno relocations in Cedar Common Runtime, caused by a kernel update from an upstream provider. Apps may have seen dynos relocate to new servers, with logs mentioning "Relocating dyno to a new server." The incident began at and continued until it was resolved at .
The provider communicated the incident via a series of updates, issuing four status updates that tracked ongoing investigation, a related provisioning issue with the Heroku Connect Add-on, and finally the deployment of a kernel update to fix the dyno relocation problem, returning Cedar Common Runtime to normal operation.
Minor
: Heroku: Intermittent routing for US apps
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(2 hours and 55 minutes)
Heroku experienced an outage affecting apps in the US region, with intermittent connectivity and timeouts for some users. The incident began at and was resolved by , lasting about 31 minutes. Engineers responded to an unexpected spike in traffic by increasing capacity, which restored routing and resolved the issue. The provider issued 2 status updates during the incident, and monitoring continued after the fix. The disruption appeared localized to US-region apps and did not indicate a global impact.
Minor
: Heroku EU routing issues briefly affected some apps
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour)
Heroku reported intermittent routing availability for some applications in the EU region, leading to degraded routing for affected apps. Users in Europe may have experienced intermittent connectivity or errors when routing requests to their apps during the incident.
The outage began at and was resolved by , lasting approximately 1 hour. The Apps component was impacted, and the status page issued 2 updates documenting the investigation and resolution as engineers worked to restore normal routing. The service returned to normal after .
