Heroku Outage History

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.

The outage began at 6:03 AM UTC with intermittent outages affecting Heroku Apps. StatusGator detected login issues at Jun 10, 2025 6:36 AM UTC, roughly 6 hours 35 minutes before the official acknowledgment. Heroku’s status page first reported the problem at Jun 10, 2025 1:11 PM UTC with the Apps component listed as down, and the issue persisted for most of the day and into the next morning. Recovery followed by Jun 11, 2025 4:56 AM UTC when the Apps component returned to up. The provider issued 2 status updates during the incident.

During the outage, users worldwide were unable to login, access dashboards, or use the API, with app hosting and related services degraded or unavailable. The event generated a high volume of user reports across multiple regions, indicating a broad and sustained disruption. The service described an initial investigation and subsequent escalation to a full outage, followed by recovery and return to normal operation by early on {{date:2025-06-11}}.

Heroku executed a short, scheduled maintenance window affecting the Apps component. The maintenance began during the morning UTC window and lasted about 40 minutes, during which the Apps were in maintenance mode. The status page documented a scheduled maintenance initially and then confirmed that maintenance was underway, followed by completion in a second update. This incident involved two official status updates and directly impacted the Apps component during the window.

Heroku investigated an issue affecting provisioning of one-off dynos in Cedar Private Spaces, which could interfere with starting new one-off dynos for affected apps. A workaround was provided: re-run failed jobs or use the heroku run command to provision a new one-off dyno. The Apps component was affected during the incident and users relying on Cedar Private Spaces may have experienced provisioning delays or errors. The provider issued two status updates as the situation developed.

An incident affected provisioning of one-off dynos in Cedar Private Spaces, potentially causing delays or failures for apps using this feature. The issue began with an investigation at May 7, 2025 4:26 PM UTC and was resolved by May 7, 2025 8:56 PM UTC, lasting about 4 hours and 30 minutes. The problem was listed as a degraded provisioning issue impacting Heroku Apps in Cedar Private Spaces. The provider issued 2 status updates during the incident as they worked to restore functionality.

An issue with the Heroku Platform API caused HTTP 503 errors for API requests and when using the Heroku Dashboard or CLI. The outage began at Apr 9, 2025 8:26 PM UTC and lasted about 1 hour and 5 minutes, with services returning to normal by Apr 9, 2025 9:31 PM UTC. The disruption affected the Platform API and related tooling, impacting developers' ability to manage apps, deployments, and data retrieval during the incident.

Heroku issued updates during the event to communicate the ongoing investigation and eventual recovery. In total, two official status updates were posted, reflecting the transition from a degraded state back to normal.

During 8:26 PM UTC to 9:01 PM UTC, Heroku experienced an issue with Application Logs that could cause log entries to be missing or not prefixed with the typical app[api] identifier. This degraded logging visibility affected the Tools component and may have left users with incomplete log records. The incident prompted an investigation and was resolved after about 35 minutes; the provider issued 2 status updates during the event, first noting the investigation and then confirming remediation as normal logging resumed.

Heroku reported an issue impacting Heroku Connect, with some users seeing their Heroku Connect instance enter a DB_UNAVAILABLE state. The Data component degraded starting at 7:46 AM UTC and was restored by 9:31 AM UTC, for a total duration of about 1 hour and 45 minutes. The incident was acknowledged with an investigation update and later marked resolved as the component returned to normal.

Heroku experienced a brief issue with data services in the EU that impacted the ability to create new database instances. The incident began at 10:26 PM UTC and was resolved by 11:01 PM UTC, lasting about 35 minutes. The EU data component entered a degraded state, and the status page reported an ongoing investigation into data services before returning to normal. The service issued two official status updates during the event, indicating progression from investigation to resolution, with impact appearing limited to the EU region.

Heroku experienced a brief ACM-related incident that caused delays in issuing TLS certificates for apps. The issue affected the Apps component and was listed as a degraded condition. The outage began at 9:36 PM UTC and was resolved by 10:11 PM UTC, lasting about 35 minutes. The status page stated: "Investigating an issue with Automated Certificate Management. Certificate issuance may be delayed." During the incident, the provider issued two status updates to track the investigation and resolution.

With ACM back to normal, certificate issuance proceeded as expected and affected apps returned to normal operation.