Statuspage: Erroneous AWS Third-Party Component Statuses
Timeline of updates
- resolved
The cause for the incorrect AWS third-party component statuses has been identified and a fix has been rolled out ensuring AWS third-party component statuses are in sync.
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: minor) posted by Statuspage, started 2018-03-20 15:01 UTC, resolved after 3.1 h, 1 update(s).
- Title
- Erroneous AWS Third-Party Component Statuses
- Vendor
- Statuspage
- Date
- URL
- https://rewindex.com/company/statuspage/incidents/k5cbfj126q6t
Statuspage profileRecent Statuspage incidentsAll outages on March 20, 2018Statuspage in March 2018MarkdownJSON