Rewindex

CompaniesVonageIncidents

Vonage: Video SIP Interconnect Issue in US-EAST-1

MinorStatus: resolvedStarted Resolved (0 min)1 updatevonageapi.statuspage.io (opens in new tab)
Part of an outage event

AWS us-east-1 outage, May 8, 2026 · 38 vendors, 43 incidents

Vonage’s incident started in the same window without naming AWS (timing only, not evidence of a link). (hop 1, posted +1 h 32 min vs AWS’s own post)

Swipe sideways to see the whole diagram.

same windowAWS us-east-1posted 00:25 UTCPosted before AWS did3 vendors, 2 blamed AWSNeon, Datadog, ConvexWithin an hour11 vendors, 11 blamed AWSChargebee, RudderStack, Canva, Logz.io +71 to 4 hours later10 vendors, 9 blamed AWSSalesforce, Dropbox Sign, Klaviyo, HubSpot +6Later2 vendors, 2 blamed AWSWiz, SingleStoreVonage (this incident)posted +1 h 32 min
same windowAWS us-east-1posted 00:25 UTCPosted before AWS did3 vendors, 2 blamed AWSNeon, Datadog, ConvexWithin an hour11 vendors, 11 blamed AWSChargebee, RudderStack,Canva, Logz.io +71 to 4 hours later10 vendors, 9 blamed AWSSalesforce, Dropbox Sign,Klaviyo, HubSpot +6Later2 vendors, 2 blamed AWSWiz, SingleStoreVonage (this incident)posted +1 h 32 min
Vonage is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["AWS us-east-1<br/>posted 00:25 UTC"]:::root
  before["Posted before AWS did<br/>3 vendors, 2 blamed AWS<br/>Neon, Datadog, Convex"]:::blames
  root --> before
  h1["Within an hour<br/>11 vendors, 11 blamed AWS<br/>Chargebee, RudderStack, Canva, Logz.io +7"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>10 vendors, 9 blamed AWS<br/>Salesforce, Dropbox Sign, Klaviyo, HubSpot +6"]:::blames
  root --> h4
  later["Later<br/>2 vendors, 2 blamed AWS<br/>Wiz, SingleStore"]:::blames
  root --> later
  me["Vonage (this incident)<br/>posted +1 h 32 min"]:::me
  root -.->|"same window"| me

Full 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

  1. resolved

    Vonage services are fully restored following today's interruption in the US-EAST-1 region and some customers may have experienced SIP call failures during this period from [2026-05-07 23:42:00] UTC until [2026-05-07 23:52:00] UTC Thank you for your patience and understanding as we worked to restore services as quickly as possible. If you have any questions, please contact api.support.vonage.com

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).

Vonage profileRecent Vonage incidentsMarkdownJSON