Vonage: Service Issue in Platform
AWS outage, Jun 13, 2023 · 56 vendors, 56 incidents
Vonage’s incident blames AWS as the cause. (hop 1, posted +35 min vs the first vendor naming AWS)
“…Service Issue in Platform The wide-spread AWS issues affecting us-east-1 (Virginia) region have been resolved. The following services were impacted June 13th at 19:01 UTC until June 13th at 21:23 UTC:…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>13 vendors, 13 blamed AWS<br/>Pipedream, Wiz, Temporal Cloud +10"]:::blames
root --> h1
h4["1 to 4 hours later<br/>7 vendors, 6 blamed AWS<br/>CockroachDB, Vanta, Asana +4"]:::blames
root --> h4
me["Vonage (this incident)<br/>posted +35 min"]:::me
h1 --- 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
The wide-spread AWS issues affecting us-east-1 (Virginia) region have been resolved. The following services were impacted June 13th at 19:01 UTC until June 13th at 21:23 UTC: SMS, 10DLC Messages API Voice transcription AI Studio - studio builder AI Studio Insights API, live telephony & messages sessions Voice Programmable SIP Domain Updates Video Inspector All services have been restored. Please let support@api.vonage.com know if you continue to experience problems with this. A post-mortem will be published in the next few days.
From Vonage’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Impact, status and times are the vendor’s own, as last archived. View on vonageapi.statuspage.io (opens in new tab).