Heroku Feature Degradation
The upstream errors have been resolved, and normal operations have been restored. This incident is now resolved.
The latest update from Heroku.
State
Resolved
Started
4 d ago
2026-10-28 10:55 UTC
Lasted
3 h 26 min
until 2026-10-28 14:21 UTC
Worst impact
Degraded
Timeline
6 updatesInvestigating
3 min 1%
Update
3 h 23 min 99%
Updates
Times in UTCAs posted by Heroku
The upstream errors have been resolved, and normal operations have been restored. This incident is now resolved.
Most upstream errors have now been addressed. If you encounter errors while building Node.js packages, please retry the build. We will provide an additional update once normal operations have been fully restored.
At this time most upstream errors and been triaged. In case of errors building nodejs packages, continue to retry. The team will post an additional update once all systems are back to normal.
Incident resolved.
Node.js builds are currently experiencing elevated error rates due to issues with an upstream dependency.
Heroku engineers are investigating.
Affected components
1Heroku in the last 90 days
Full historyIncidents in 90 days
5
Days with an incident
5
Median duration
52 min
This incident
4.0× the median
Other Heroku incidents
All incidentsHeroku·Heroku Feature Degradation
Incident resolved.
Heroku·Heroku Service Degradation
Engineers have remediated the issue.
Heroku·Heroku Retroactive Feature Degradation
The issue is now resolved.
Heroku·Heroku Retroactive Feature Degradation
Between 11:01 UTC on August 6, 2026 and 13:10 UTC on August 6, 2026, we identified a performance issue affecting Heroku release phase deploys. During this time, some customers experienced delayed completion of release phase commands during deploys, with some remaining in an `release phase executing` state longer than expected. We have confirmed that the issue is resolved. We apologize for how you and your business may have been affected by this incident. We will thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
Follow Heroku
Your coding agent knows when Heroku is down, and tells you when a failure is theirs, not yours. You can also get Heroku incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "heroku" and tell me if Heroku has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=heroku/feed subscribe https://outages.cc/feed.xml?providers=herokuFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane