Vendor reports: operationalResolved · vendor status “resolved”Official status API
Post-Incident Notification - RTCx Services - US
Reported by Sinch · Communication & Messaging · source last read 3 min ago
- Vendor start
- Oct 1, 2026, 10:28 UTC
- Vendor's clock
- Resolved
- Oct 1, 2026, 06:00 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- Not available
- Needs both vendor times
Summary
Built from the facts below, no AI
Potential impact, not a confirmed outage of your systems.
What the vendor confirmed
What is unknown
Last update in these facts: 2026-10-01 10:28 UTC · summary s1, evidence 38cea92dc44487ae
Evidence (7)
- E1Sinch reports operational. (vendor) source (opens in a new tab)
- E2Vendor title: "Post-Incident Notification - RTCx Services - US". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2026-10-01 10:28 UTC. (vendor) source (opens in a new tab)
- E5The vendor did not state which regions are affected. (Statuswall)
- E6The vendor attached no components. (Statuswall)
- E7Vendor-reported resolution: 2026-10-01 06:00 UTC. (vendor) source (opens in a new tab)
Affected scope
Not stated by the vendor
Components: not stated by the vendor
No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.
Potential relevance
Sinch is not in your stack. Follow it to see whether reports like this fall inside the regions you use.
Timeline
Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.
- Oct 1, 2026, 06:00 UTCVendor-reported resolutionVendor time
- Oct 1, 2026, 10:28 UTCVendor-reported startVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.