APIs: messaging, media, analytics
Degraded / minor incident Vonage API status
vonage.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
Vonage API's status page shows “Degraded / minor incident” in Messages API and SMS Europe; the vendor is resolved. User reports haven't spiked, so wide impact isn't visible yet. Amazon Web Services, a provider it may run on (inferred), also reports trouble. Coincidence, not causation.
confidence: low Vendor: minor issue · users: normal · routing: no data · upstream providers: major.
- Vendor status page Degraded / minor incident · 3 open incidents
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) Amazon Web Services: Major outage
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Messages API, SMS Europe
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 22 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | 1 h 55 min |
Evidence
- Official page: Degraded / minor incident (“Partially Degraded Service”). evidence confidence: high
- Vendor stage: resolved on “Issues Impacting WhatsApp API”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
- Amazon Web Services reports an issue. Vonage API may depend on it (inferred from public sources). Coincidence, not causation. evidence confidence: low
What we don't know: what is happening inside Vonage API's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.
Coincidence, not causation: signals that overlap in time are shown side by side, not as proof of cause.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: minor issue · users: normal · routing: no data · upstream providers: major. Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal).
Who depends on whom
Vonage API may run on Amazon Web Services (inferred). We don't map other services that depend on Vonage API. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Vonage API or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Vonage API. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Issues Impacting WhatsApp API
minor resolved · started · resolved
9 updates
- investigating
We are working to resolve the issue that is impacting Vonage Messages API – WhatsApp channel. Messages API customers may not receive delivery callbacks for the WhatApp channel. Outbound messaging is unaffected. Inbound WhatsApp messages are affected. We'll continue to provide further updates here within 60 minutes. Thank you for your patience and understanding. If you have any questions, please contact api.support.vonage.com.
- investigating
We continue to work to resolve the issue that may be impacting your access to WhatsApp messaging. We'll continue to provide further updates here within 60 minutes. Thank you for your patience and understanding. If you have any questions, please contact api.support.vonage.com.
- investigating
We continue to work to resolve the issue that may be impacting Vonage Messages API – WhatsApp channel. We'll continue to provide further updates here within 30 minutes. Thank you for your patience and understanding. If you have any questions, please contact api.support.vonage.com.
- identified
We have identified the issue that may be impacting your ability to access WhatsApp, and we are working with our partner on a resolution. We will continue to provide further updates within 30 minutes and once full service is restored. Thank you for your patience and understanding. If you have any questions, please contact api.support.vonage.com.
- identified
We have identified the issue that is affecting inbound WhatsApp messages and webhooks, and we are working with our partner on a resolution. We will continue to provide further updates within 30 minutes and once full service is restored. Thank you for your patience and understanding. If you have any questions, please contact api.support.vonage.com.
- identified
We have identified the issue that is affecting inbound WhatsApp messages and webhooks, and we are working with our partner on a resolution. We will continue to provide further updates within 30 minutes and once full service is restored. Thank you for your patience and understanding. If you have any questions, please contact api.support.vonage.com.
- identified
We have identified the issue that is affecting inbound WhatsApp messages and webhooks, and we are working with our partner on a resolution. We will continue to provide further updates within 30 minutes and once full service is restored. Thank you for your patience and understanding. If you have any questions, please contact api.support.vonage.com.
- monitoring
Vonage services show signs of recovery following today's interruption in inbound WhatsApp messages and webhooks. We'll continue to provide further updates here within 30 minutes and once full service is restored. Thank you for your patience and understanding as we work to restore services as quickly as possible. If you have any questions, please contact api.support.vonage.com.
- resolved
Vonage services have been fully restored following today's service interruption affecting inbound WhatsApp messages and webhooks, which began at 2026-11-13 18:31:00 UTC. Full resolution has been confirmed effective 2026-11-13 22:00:00 UTC. Please note inbound messages sent and callbacks not received during the incident are lost. Impacted customers will receive a formal RFO. 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.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.