Rewindex

CompaniesVonageIncidents

Vonage: Service issue in Voice API platform

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

AWS outage, Jul 16, 2026 · 27 vendors, 29 incidents

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

Swipe sideways to see the whole diagram.

blamed Anthropicsame windowAWSposted 08:44 UTCPosted before AWS did2 vendors, 1 blamed AWSFusionAuth, UpstashWithin an hour2 vendors, 2 blamed AWSCoda, GrammarlyAnthropicposted −5 min, did not name AWSGitHub, GitHub Copilot+12 h 21 minVonage (this incident)posted −38 min
blamed Anthropicsame windowAWSposted 08:44 UTCPosted before AWS did2 vendors, 1 blamed AWSFusionAuth, UpstashWithin an hour2 vendors, 2 blamed AWSCoda, GrammarlyAnthropicposted −5 min, did not nameAWSGitHub, GitHub Copilot+12 h 21 minVonage (this incident)posted −38 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<br/>posted 08:44 UTC"]:::root
  before["Posted before AWS did<br/>2 vendors, 1 blamed AWS<br/>FusionAuth, Upstash"]:::blames
  root --> before
  h1["Within an hour<br/>2 vendors, 2 blamed AWS<br/>Coda, Grammarly"]:::blames
  root --> h1
  p0["Anthropic<br/>posted −5 min, did not name AWS"]:::timing
  root -.-> p0
  k0["GitHub, GitHub Copilot<br/>+12 h 21 min"]:::hop2
  p0 -->|"blamed Anthropic"| k0
  me["Vonage (this incident)<br/>posted −38 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 impacting WebSocket connections in the EU and APAC regions where authentication headers were not being sent have been fully restored following the service interruption, which began at [2026-07-01 16:16] UTC. Full resolution has been confirmed effective [2026-07-16 08:53] UTC. Thank you for your patience and understanding as we worked to restore services. 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