Rewindex

CompaniesVonageIncidents

Vonage: USA SMS - Delivery degradation affecting US AT&T Network

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

Google Cloud outage, Aug 6, 2025 · 12 vendors, 12 incidents

Vonage’s incident started in the same window without naming Google Cloud (timing only, not evidence of a link). (timing only, posted +50 min vs the first vendor naming Google Cloud)

Swipe sideways to see the whole diagram.

blamed Twiliosame windowGoogle Cloudown incident not archivedWithin an hour4 vendors, 2 blamed Google CloudTemporal Cloud, Confluent, Grafana Cloud,JFrog1 to 4 hours later1 vendor, 1 blamed Google CloudBasetenTwilioposted +42 min, did not name Google CloudBrex, Close+2 h 3 min to +5 h 16 minVonage (this incident)posted +50 min
blamed Twiliosame windowGoogle Cloudown incident not archivedWithin an hour4 vendors, 2 blamed GoogleCloudTemporal Cloud, Confluent,Grafana Cloud, JFrog1 to 4 hours later1 vendor, 1 blamed GoogleCloudBasetenTwilioposted +42 min, did not nameGoogle CloudBrex, Close+2 h 3 min to +5 h 16 minVonage (this incident)posted +50 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["Google Cloud<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>4 vendors, 2 blamed Google Cloud<br/>Temporal Cloud, Confluent, Grafana Cloud, JFrog"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>1 vendor, 1 blamed Google Cloud<br/>Baseten"]:::blames
  root --> h4
  p0["Twilio<br/>posted +42 min, did not name Google Cloud"]:::timing
  root -.-> p0
  k0["Brex, Close<br/>+2 h 3 min to +5 h 16 min"]:::hop2
  p0 -->|"blamed Twilio"| k0
  me["Vonage (this incident)<br/>posted +50 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

    This incident has been resolved.

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