Rewindex

CompaniesVonageIncidents

Vonage: Verify Requests Via Email Are Failing

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

Cloudflare outage, Dec 5, 2025 · 46 vendors, 46 incidents

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

Swipe sideways to see the whole diagram.

same windowCloudflareown incident not archivedWithin an hour18 vendors, 18 blamed CloudflareUnbounce, Expo, GitLab +151 to 4 hours later1 vendor, 1 blamed CloudflareKlaviyoLater2 vendors, 2 blamed CloudflareBitrise, Sigma ComputingVonage (this incident)posted +42 min
same windowCloudflareown incident not archivedWithin an hour18 vendors, 18 blamedCloudflareUnbounce, Expo, GitLab +151 to 4 hours later1 vendor, 1 blamed CloudflareKlaviyoLater2 vendors, 2 blamed CloudflareBitrise, Sigma ComputingVonage (this incident)posted +42 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["Cloudflare<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>18 vendors, 18 blamed Cloudflare<br/>Unbounce, Expo, GitLab +15"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>1 vendor, 1 blamed Cloudflare<br/>Klaviyo"]:::blames
  root --> h4
  later["Later<br/>2 vendors, 2 blamed Cloudflare<br/>Bitrise, Sigma Computing"]:::blames
  root --> later
  me["Vonage (this incident)<br/>posted +42 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

    Our team identified the root cause with the email service provider, and the issue has been fully remediated. During the incident, customers would not have received the verify emails. With the service restored, customers should no longer experience any degradation in Verify Email requests. Start time: 08:48 UTC End time: 09:18 UTC Please let support@api.vonage.com know if you continue to experience problems with this.

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