Live / Heroku / Incident
Heroku: Resolved: Heroku Feature Degradation
Heroku · heroku.comResolved2026-10-28 15:59 UTC
Public — what happened
Summary
Heroku said that on 2026-10-28 starting at 10:55 UTC it was looking into a feature degradation, and shortly afterward reported that Node.js builds were seeing more errors than usual. The company attributed the problem to an upstream dependency, meaning a service outside Heroku. By 15:02 UTC it said most of those errors had been handled and advised customers to retry any failed Node.js package builds. Heroku said the upstream errors were resolved and normal operations were restored at 15:59 UTC.
Timeline
- Started — 2026-10-28 10:55 UTC
- Investigating — 2026-10-28 10:55 UTC (2 updates)
- Resolved — 2026-10-28 15:59 UTC · 5h 04m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Heroku against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Heroku: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Heroku report →
More from Heroku
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.