← Live dashboard

Resolved: Heroku Retroactive Feature Degradation

ResolvedminorOfficial source confirmedFirst recorded update Feb 23, 2026, 11:31 PM · Resolved Feb 23, 2026, 11:31 PM

Customers using Heroku in the Common Runtime may have experienced intermittent dyno disruptions earlier today between 17:50 UTC and 20:24 UTC. The issue has been resolved after we disabled a related service and rolled back a recent change. We’re validating the update in lower environments and will continue monitoring for stability.

Heroku live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Heroku now? Check the current status

Updates (1)

  1. Feb 23, 2026, 11:31 PM
    Resolved: Heroku Retroactive Feature Degradation

    Customers using Heroku in the Common Runtime may have experienced intermittent dyno disruptions earlier today between 17:50 UTC and 20:24 UTC. The issue has been resolved after we disabled a related service and rolled back a recent change. We’re validating the update in lower environments and will continue monitoring for stability.

    Heroku ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow Heroku's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.