Statuspage: Incident timestamps showing incorrect data
Timeline of updates
- resolved
We discovered an issue with a deployment that caused the timestamps on incidents to show incorrectly in the management portal. We rolled back this code and all timestamps are showing correctly now.
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-01-30 18:30 UTC, resolved after 0 min, 1 update(s).
- Title
- Incident timestamps showing incorrect data
- Vendor
- Statuspage
- Date
- URL
- https://rewindex.com/company/statuspage/incidents/vwqnj8mr2lwd
Statuspage profileRecent Statuspage incidentsAll outages on January 30, 2020Statuspage in January 2020MarkdownJSON