rewindex

ChangesHerokuHeroku Feature Degradation

Heroku: Incident updated: Heroku Feature Degradation

Incident updateNormal progress (rule, 100%)Changed status.heroku.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Heroku removed; blue is what they added. Muted text is unchanged context.

AddedUpdateinvestigating#1
Before: not present
After: <p>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.</p>

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

Wednesday, October 28

3 incident changes

Cite this

Incident updated: Heroku Feature Degradation on Heroku’s status page, changed 2026-10-28 15:13 UTC (change 1 of 3).

Title
Incident updated: Heroku Feature Degradation
Vendor
Heroku
Date
URL
https://rewindex.com/change/rfb7e967304aedd

All Heroku changesHeroku profileMarkdownJSON