Statuspage: Users are unable to subscribe to incidents from the incident page
Timeline of updates
- resolved
A code change that was rolled out at 10:30 AM yesterday caused subscribing to incidents from the incident page to fail. A fix has been deployed and this issue is now resolved.
From Statuspage’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on metastatuspage.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Statuspage, started 2020-02-12 21:06 UTC, resolved after 0 min, 1 update(s).
- Title
- Users are unable to subscribe to incidents from the incident page
- Vendor
- Statuspage
- Date
- URL
- https://rewindex.com/company/statuspage/incidents/pbxb6r36lkkf
Statuspage profileRecent Statuspage incidentsAll outages on February 12, 2020Statuspage in February 2020MarkdownJSON