Heroku Outage History

Heroku experienced a brief degraded performance affecting apps in the US Virginia region, including Common, Private Spaces, and Fir runtimes. Users in Virginia may have encountered errors or delays. The degradation began at 8:11 PM UTC and was resolved by 9:06 PM UTC after the provider reported external connectivity issues in the region and subsequently restored services. The incident included two official status updates during its course.

Heroku ran a scheduled maintenance window that affected the Apps component. The maintenance began at 9:00 AM UTC and concluded at 10:36 AM UTC, lasting approximately 1 hour 36 minutes. During this period, users hosting apps on Heroku may have experienced temporary interruptions or degraded performance as maintenance proceeded.

Heroku issued 2 status updates during the incident, confirming the maintenance and its completion. The Apps component returned to normal at 10:36 AM UTC.

Heroku conducted a scheduled maintenance window affecting the Apps component. The maintenance began at Aug 13, 2025 12:01 AM UTC and concluded by Aug 13, 2025 1:01 AM UTC, lasting about one hour. The status page posted a maintenance notice at Aug 13, 2025 12:00 AM UTC and later updated to confirm the maintenance was underway, with normal operations resumed after the window.

Beginning on Jul 18, 2025 10:00 PM UTC, some Heroku customer apps began experiencing uneven load distribution across dynos, resulting in increased latency and timeouts. On Aug 1, 2025 2:16 PM UTC, the Heroku status page reported an outage for the Apps component, which briefly transitioned to down before recovering by Aug 1, 2025 2:31 PM UTC. The incident was resolved within about 15 minutes, with the status page providing updates as the issue progressed.

Starting July 17, 2025, some Heroku customer apps began experiencing uneven load distribution to dynos, leading to increased request latency and timeouts. The incident persisted and was reflected in the status page as an outage for the Apps component, beginning at 2025-07-22T18:41:00Z and lasting until 2025-07-23T01:36:00Z, for a duration of about 6 hours and 55 minutes. Engineers worked to resolve the routing issue and restore normal service.

Heroku Automated Cert Management (ACM) experienced delays in issuing and renewing SSL/TLS certificates due to an outage with a third-party provider. Customers issuing new certificates or renewals may have seen longer wait times and certificates becoming active later than expected.

The incident began at 10:41 PM UTC and was resolved by 4:31 PM UTC, lasting about 18 hours and 50 minutes. ACM stabilized at 4:47 AM UTC before full recovery. Heroku published four status updates during the incident, and the issue primarily affected the Tools component within ACM, impacting certificate issuance and renewal workflows across customers.

Heroku reported degradation on data.heroku.com dashboards, including Dataclips and the Postgres Data Dashboard. Some customers experienced inconsistent loading of dashboards while databases were unaffected. The degradation began at Jul 16, 2025 6:16 PM UTC and was resolved by Jul 16, 2025 9:51 PM UTC, lasting about 3 hours and 35 minutes.

The status page posted two updates during the incident, noting the Data component degraded and then returned to normal. A user reported Dataclips not loading around 6:39 PM UTC during the event.

The Heroku Common Runtime experienced a degraded condition in the US region, with application processes continuing to run after their dynos were scaled down. These processes are not visible via heroku ps but may cause side effects like continued logging for affected apps. The incident began on 6:16 PM UTC and was resolved by 8:06 PM UTC, lasting roughly 1 hour and 50 minutes. The issue affected the Apps component, and Heroku posted two status updates during the incident to communicate investigation progress and the restoration of normal service.

From Jun 18, 2025 4:31 PM UTC to Jun 19, 2025 1:01 AM UTC, Heroku experienced issues with dyno formations and autoscaling. Customers may have observed inconsistencies in the number of dynos running and autoscaling not triggering as expected, potentially impacting app performance and reliability across affected apps.

Heroku logged two status updates during the incident as engineers investigated the issue. The Tools and Apps components were affected (both moved from up to warn) before the service returned to the up state. The outage lasted about 8 hours and 30 minutes.

An outage hit the Heroku Apps component beginning at 6:03 AM UTC, causing intermittent issues with login, dashboards, and app access for users worldwide. By Jun 10, 2025 1:11 PM UTC the status page showed a full outage for the Apps component, affecting users across North America, Europe, and Asia. The disruption lasted about 22 hours and 53 minutes before restoration.

Heroku issued two official status updates during the incident to communicate investigation and remediation efforts. The service was fully restored by Jun 11, 2025 4:56 AM UTC. The event reflected a global impact across the ecosystem, with widespread reports of login failures and inability to access apps, dashboards, or the CLI.