Heroku Outage History

Heroku conducted a scheduled maintenance window affecting the Apps component. The maintenance began at 10:16 AM UTC and completed by 10:56 AM UTC, lasting 40 minutes. During this period, users may have experienced brief service interruptions as the Apps component transitioned through maintenance and back to normal operation. The provider issued two status updates: one noting that maintenance was underway and a follow-up confirming the Apps component had returned to full operation. This was a planned maintenance event with no broader impact beyond the scheduled window.

Heroku reported an issue affecting provisioning of one-off dynos in Cedar Private Spaces. The problem could cause failures when creating temporary dynos for apps, interrupting workflows that rely on quick, ephemeral dynos. As a workaround, engineers suggested re-running failed jobs or provisioning a new one-off dyno with heroku run. The outage began at May 8, 2025 12:21 AM UTC and was resolved by May 8, 2025 6:16 PM UTC, lasting roughly 17 hours and 55 minutes. The Apps component was affected during this period, and two official updates were posted as the incident unfolded.

Heroku faced a provisioning issue for one-off dynos in Cedar Private Spaces, potentially delaying or preventing ephemeral dynos from starting for apps. This could affect workflows that rely on one-off dynos for tasks such as build steps or run commands.

Timeline: The incident began at May 7, 2025 4:26 PM UTC when engineers began investigating provisioning problems within the Apps component. The issue was resolved by May 7, 2025 8:56 PM UTC, lasting roughly 4 hours and 30 minutes. During the incident, the status page posted two updates documenting the investigation and restoration. The impact appeared contained to Cedar Private Spaces, with no wider service disruption reported.

From 8:26 PM UTC to 9:31 PM UTC, the Heroku Platform API experienced an outage centered on the Tools component, with HTTP 503 errors reported for API requests as well as when using the Heroku Dashboard or CLI. The disruption affected deployment workflows and API-based integrations for about 1 hour and 5 minutes before service was restored. The incident was publicly documented on the Heroku status page as an issue with the Platform API, with engineers actively investigating and working to restore normal service.

Heroku reported an incident in the Tools component affecting Application Logs, where logs normally preceded with the app[api] identifier may not appear. This degraded the ability for developers to correlate log lines with their applications.

The incident started at 8:26 PM UTC and was resolved by 9:01 PM UTC, during which the Tools component moved from up to degraded and back as engineers investigated and resolved the issue. The provider issued 2 status updates over the course of the incident.

The incident affected Heroku Connect, with the Data component briefly entering a degraded state (DB_UNAVAILABLE). The outage began on Mar 18, 2025 7:46 AM UTC and was resolved by Mar 18, 2025 9:31 AM UTC, lasting approximately 1 hour 45 minutes. During the window, the status page noted an investigation by engineers and the Data component transitioning from up to warn, with two official status updates issued. The impact was limited to Heroku Connect data integration; no broader service outages across the platform were reported.

Heroku reported a brief degradation of data services in the EU, with customers potentially unable to create new database instances. The Data component entered a degraded state at Mar 14, 2025 10:26 PM UTC and was restored by Mar 14, 2025 11:01 PM UTC, lasting about 35 minutes. The incident appeared regional to the EU and did not indicate a broader impact. The provider issued 2 status updates during the event: first noting Investigating an issue with data services, and later confirming the data services were restored.

Heroku experienced a brief issue with Automated Certificate Management (ACM) that could delay issuing certificates for apps. The incident appeared limited to ACM functions and did not indicate a platform-wide outage. The incident began at 9:36 PM UTC and was resolved by 10:11 PM UTC, with two status updates issued during the event. Impact was primarily to certificate provisioning rather than core app functionality, so users may have experienced delays when issuing or renewing TLS certificates during the window.

Heroku reported a degraded webhook delivery issue for the Apps component, causing delays in webhook events reaching connected services and automation workflows. The incident began at Feb 24, 2025 11:46 PM UTC and lasted until Feb 25, 2025 11:21 AM UTC, a duration of roughly 11 hours and 35 minutes. The status page indicated the issue with delayed delivery and the Apps component was briefly listed as degraded before being restored.

Two official status updates were published during the incident, and the Apps status transitioned from up to warn and back to up.

A brief incident affected Heroku Webhooks, causing delays in webhook deliveries for Apps. The issue began at 10:46 PM UTC and was resolved by 10:57 PM UTC after engineers investigated the cause. The status page issued two updates during the event, first noting the investigation and later confirming resolution. The impact was limited to webhook delivery timing for users, with no broader service disruption.