Heroku Outage History

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.

Heroku reported a partial outage affecting Apps due to delayed delivery of webhooks. This could cause delays or missed webhook events for apps relying on external integrations. The incident began when the status was raised to warning at 11:46 PM UTC and was resolved by 11:21 AM UTC, lasting about 11 hours 35 minutes. The provider issued two status updates during the incident, tracking the progression from delay to restoration.

Heroku experienced a brief Webhooks delay affecting the Apps component, causing webhook deliveries to be slower for some users. The incident began at 10:46 PM UTC and was resolved by 10:57 PM UTC, lasting about 11 minutes. The provider issued two status updates during the incident—one noting an investigation and a later update confirming resolution. The issue was contained to Webhooks within the Apps component and did not indicate broader service impact.

Heroku experienced a partial outage affecting the creation of Review Apps. Existing Heroku apps, services, the Dashboard, and the CLI were not affected, so users could continue most workflows aside from creating new Review Apps. The disruption was isolated to the Review Apps creation flow.

Heroku reported an issue with data.heroku.com that affected Dataclips across all regions. Users without active sessions on data.heroku.com were shown redirect loops, disrupting access to data and Dataclips workflows. The incident began at Jan 9, 2025 3:35 PM UTC and was resolved by Jan 9, 2025 5:01 PM UTC, lasting about 1 hour and 26 minutes.