21,228 outages in February - Here are the biggest:

Learn more
magnifying glass icon
magnifying glass icon
  • Can't find service? Request service
    magnifying glass icon
    Sign Up
    Home • Service directory • Heroku • Outage History
    Heroku icon
    Heroku icon

    Heroku Outage History

    Heroku is up

    There were 34 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 icon Minor

    : Heroku service disruption affects Apps and Data for 1h20m

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (1 hour and 20 minutes)

    The incident impacted Heroku's Apps and Data components, likely causing interruptions for users attempting to run apps or access data. The outage began at and was resolved by , lasting about 1 hour and 20 minutes.

    Heroku's status page documented two updates during the event. The initial update at noted a service disruption and that engineers were investigating. A follow-up update at indicated recovery, with the Apps and Data components returning to normal. The incident involved two components and was resolved without extended regional impact.

    User reports were limited, reflecting a relatively contained issue. Overall, the outage status progressed from a disruption to normal service within the 1 hour 20 minute window.

    minor icon 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.

    minor icon Minor

    : Heroku global login and API access disruption

    Detected by StatusGator: (20 minutes earlier)
    Officially acknowledged:
    Outage ended: (1 hour and 36 minutes)

    StatusGator detected login and CLI access issues for Heroku at , about 21 minutes before the official acknowledgement at . The early warning ended at . The disruption affected the Tools component and impacted users globally, hindering login, API use, CLI commands, and dashboard access. The first official update appeared at indicating engineers were investigating and that the Tools component had degraded. The incident was resolved by when the Tools component returned to up, signaling recovery. The provider issued 2 status updates during the incident.

    major icon Major

    : Heroku outage disrupts Salesforce cloud services across products

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (19 hours and 27 minutes)

    An outage affected the Heroku platform and multiple Salesforce cloud services, including Commerce Cloud, Core services, Hyperforce, MuleSoft, Marketing Cloud, Slack, and Tableau. The disruption impacted app hosting, data processing, and integrations for many customers. The outage began on and was resolved by , lasting about 19 hours and 27 minutes. Affected components included Tools, Data, and Apps.

    Salesforce's status updates indicated the issue was triggered by a third-party vendor, with engineers working to resolve the disruption. The provider issued three official updates during the incident before restoration, noting ongoing remediation and eventual recovery.

    major icon Major

    : Heroku Apps outage affecting US & EU with elevated H99 errors

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (1 hour and 5 minutes)

    Heroku reported an outage impacting the Apps component of the platform due to elevated H99 errors in the runtime, affecting users in the US and EU. The issue began at and resulted in applications failing to start or respond in those regions.

    Status updates documented the incident: The first update at indicated investigation into elevated H99 errors. A subsequent update at showed the Apps component had recovered, returning to a normal state. The outage lasted roughly 2 hours and 59 minutes.

    major icon Major

    : Heroku Apps outage hits US and EU regions

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (50 minutes)

    The Heroku Apps component experienced an outage starting at with elevated H99 errors affecting US and EU regions, causing downtime for user applications. The Apps component was later reported down from and was restored by as engineers worked to resolve the issue. The outage lasted about 1 hour and 21 minutes and affected users across two regions.

    minor icon Minor

    : Heroku AI responses degraded in US region, then restored

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (9 hours and 20 minutes)

    The Heroku Data component in the US region experienced a brief degradation as API responses from the gpt-oss-120b model declined. Users may have encountered slower or failing API calls during the incident window. The outage began at and was resolved by , lasting approximately 9 hours and 20 minutes.

    Heroku issued 2 status updates during the incident, first noting an investigation into the issue and later confirming restoration of normal service. The impact was focused on the US region and affected the Data component.

    minor icon Minor

    : Heroku DNS issues hinder new apps and domain provisioning

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (19 hours and 10 minutes)

    The incident affected Heroku DNS for New Apps and Domains, making DNS names for new apps and domains unreachable and causing delays provisioning DNS records. The issue began on and continued until , lasting about 19 hours and 10 minutes. Users attempting to provision new apps or add custom domains were impacted, with delays centered on DNS record provisioning. The Apps component was listed with a degraded status during the event, and the provider issued two status updates—one announcing an investigation and a later one noting restoration of service.

    minor icon Minor

    : Heroku Cedar Common Runtime dyno relocations and Connect Add-on provisioning issue

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (2 days and 50 minutes)

    Heroku experienced degraded performance across the Cedar Common Runtime due to a kernel update from an upstream provider, which caused increased dyno relocations. Apps could see logs stating 'Relocating dyno to a new server', potentially affecting runtime stability and deployments. Separately, Heroku Connect Add-on provisioning had issues in the US and EU, with a workaround to cancel during step 2 and refresh the page.

    Timeline and duration: The Apps component moved to a degraded state at . Tools progressed to up by , while Apps remained affected until , for a total duration of roughly 54 hours. The provider issued 4 official status updates during the incident.

    Geographic and user impact: The Connect Add-on issues were region-specific to the US and EU, while Cedar Common Runtime dyno relocations affected apps more broadly. All components were restored by . Users may have experienced intermittent disruptions or deployment delays during the degraded period.

    minor icon Minor

    : Heroku intermittent routing affects US-region apps

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (2 hours and 55 minutes)

    Heroku reported intermittent routing issues impacting applications hosted in the US region, causing timeouts for some users. The outage began at and appeared to be resolved by after capacity scaling reduced the traffic spike. The incident continued to be tracked on the status page, with the Apps component listed in a degraded state until full restoration by . The provider issued 2 status updates during the event, and the issue primarily impacted US-region deployments.

    Heroku icon

    Looking for more Heroku outage stats?

    Get real-time insights and historical data on Heroku outages.

    Looking to track Heroku downtime and outages?

    • Receive real-time status updates
    • Show current status on private or public status page
    • Be the first to know if service is down
    • Keep your team informed
    • Monitor alongside other services and websites
    Start monitoring for free