Statuspage: Delayed delivery of Incident notifications via email
Timeline of updates
- resolved
We experienced a delay in delivery of notifications of incidents for a period of 15 minutes which has been resolved. We have identified the cause of this is an ongoing incident with one of our messaging vendors, and we have migrated all possible notification traffic to our alternate messaging vendors.
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 this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
d23a4dc786347cfd…
Impact, status and times are the vendor’s own, as last archived. View on mstspg.co (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Statuspage, started 2023-02-21 18:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Delayed delivery of Incident notifications via email
- Vendor
- Statuspage
- Date
- URL
- https://rewindex.com/company/statuspage/incidents/zh4w3w90c6g5
Statuspage profileRecent Statuspage incidentsAll outages on February 21, 2023Statuspage in February 2023MarkdownJSON