Skip to main content
Chrome icon

New! Check service status instantly with our Chrome extension

Add to Chrome External link icon
Firefox icon

New! Check service status instantly with our Firefox extension

Add to Firefox External link icon
magnifying glass icon
magnifying glass icon
  • Can't find service? Request service
    Sign up
    Heroku icon
    Heroku icon

    Heroku outage history

    Platform for deploying, managing, and scaling cloud applications.

    There were 40 Heroku outages since January 2025 which are summarized below, including incident details, duration, and resolution information.

    Not working for you?

    minor icon Minor

    : Heroku Tokyo Private Spaces face dyno restart and scaling issues

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (3 hours and 5 minutes)

    Heroku reported degraded performance in Private Spaces in the Tokyo region beginning at . Customers may have been unable to restart dynos or scale up because new instances could not boot, while already-running dynos were not expected to be affected.

    Heroku attributed the incident to an upstream cloud provider and monitored its recovery. The provider reported partial recovery in the following hours, though some restart and scaling failures could continue. Heroku marked the incident resolved at .

    minor icon Minor

    : Heroku Tools degradation impacts Node.js builds, resolved

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

    The Heroku Tools component experienced degraded performance, causing elevated error rates for Node.js builds due to issues with an upstream dependency. The degradation began at and persisted as engineers investigated and triaged upstream errors. Build attempts involving Node.js packages may have failed or timed out during this period.

    Throughout the afternoon, Heroku provided updates noting ongoing investigation and advising users to retry builds if they encountered errors. By , most upstream errors had been addressed, and a final note indicated that normal operations would be resumed with retries as needed. The Tools component returned to normal at .

    minor icon Minor

    : Heroku logs intermittently drop in US region; restoration complete

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

    Impact began at with intermittent loss of application logs for some Heroku Common Runtime customers in the US region. In a subset of US regions, router logs were dropped while app logs remained available, causing degraded observability for affected apps and workflows. The issue persisted for about three hours as engineers investigated and worked to restore normal log delivery.

    By engineers had fixed the underlying fault and began monitoring, with full restoration of log delivery by . The incident was confined to US regions and affected log routes rather than overall app availability.

    minor icon Minor

    : Heroku EU TLS handshake failures disrupt apps

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

    An EU-region issue affected Heroku's Common Runtime apps when a security update unintentionally tightened TLS certificate policy for app default domains (<app>.herokuapp.com). This caused TLS handshake failures and prevented some clients from connecting to apps. The impact began at and degraded access for about an hour as engineers worked on remediation. Engineers subsequently identified the policy regression and moved to remediate it, with changes taking effect around and full recovery by .

    minor icon Minor

    : Heroku feature degradation briefly impacts apps

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

    An incident affected Heroku Apps, causing partial degradation of app functionality for hosted projects. The issue began at when Heroku flagged a feature degradation and said engineers were investigating. The disruption lasted about 30 minutes and was resolved by as services returned to normal and app behavior stabilized. The status updates described the event as a feature degradation and confirmed that the engineering team was actively working on root cause and remediation.

    During the incident, Heroku provided updates noting the degraded feature within the Apps component, and later stated the issue had been resolved and systems were operating normally again. The impact appeared limited to applications relying on the affected feature, with users likely noticing intermittent or degraded functionality during the window.

    minor icon Minor

    : Heroku Cedar Private Spaces dynos affected by upstream outage

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

    A disruption affected Cedar Private Spaces apps hosted in Virginia, where users experienced failures when starting and scaling dynos. The disruption began at as Heroku noted engineers were investigating.

    At , engineers identified an upstream service provider issue that was impacting Cedar Private Spaces in Virginia. They were working with the upstream provider to expedite a resolution. A follow-up at indicated some service recovery had been observed and that teams were monitoring for full resolution.

    Finally, the status was updated to indicate recovery as services returned to normal by . The impact appeared regional to Virginia, with no widespread outages reported.

    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: (15 minutes earlier)
    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: (15 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.

    Similar services

    Heroku icon

    Looking for more Heroku outage stats?

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

    Heroku outage stats