Sinch: Site US7 & BR2 - Degradation
Azure outage, Jan 25, 2023 · 14 vendors, 14 incidents
Sinch’s incident started in the same window without naming Azure (timing only, not evidence of a link). (timing only, posted +1 h 16 min vs the first vendor naming Azure)
“…& BR2 - Degradation No additional impact has been observed since our previous update. The Azure team has closed the incident, and we will proceed to resolve this incident. Incident start time: 2023-01…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Azure<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>1 vendor, 1 blamed Azure<br/>MongoDB Atlas"]:::blames
root --> h1
h4["1 to 4 hours later<br/>3 vendors, 2 blamed Azure<br/>Grafana Cloud, Retool, InfluxData (InfluxDB Cloud)"]:::blames
root --> h4
me["Sinch (this incident)<br/>posted +1 h 16 min"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- resolved
No additional impact has been observed since our previous update. The Azure team has closed the incident, and we will proceed to resolve this incident. Incident start time: 2023-01-25 07:05 UTC Incident end time: 2023-01-25 08:30 UTC
From Sinch’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 status.sinch.com (opens in new tab).