Skip to content
UpButler
ProductAgentsStatus pagesDocsPricing
Sign inStart free

Is Vonage down?

Vonage is having issues

Right now

Partly. China SMS - Delivery degradation of Pre-Registered brands.

Last checked (2026-10-10 07:16 UTC) from vonageapi.statuspage.io · every 180s

For agents

proceed

Proceed, expect slow or flaky responses.

GET upbutler.com/status/vonage/status.agent.json

MCP: upstream_status {"service":"vonage"}

SMS, voice, verify and video APIs (formerly Nexmo).

What Vonage says

Degraded· 1 open incident

Taken as is from Vonage's own status page API. Incident titles and component names below are theirs.

Open vonageapi.statuspage.io

What UpButler measured

There is no keyless endpoint of Vonage that says anything useful, so UpButler does not probe it. To check your own Vonage account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Open at Vonage

Text written by Vonage, shown unchanged.

Which part of Vonage?

Vonage components

1 of 80 not operational

Video

  • Session ConnectionOperational
  • Archiving (Standard)Operational
  • Archiving (Enterprise)Operational
  • Broadcast (HLS/RTMP)Operational
  • Monitoring CallbacksOperational
  • SIP InterconnectOperational
  • Advanced Firewall Control (TURN) (Standard)Operational
  • Advanced Firewall Control (TURN) (Enterprise)Operational
  • China RelayOperational

Voice

  • Programmable SIP & SIP InterconnectOperational
  • Voice APIOperational
  • Legacy TTSOperational
  • SIP TrunkingOperational
  • Voice WebRTCOperational
  • SIP EndpointsOperational
  • Advanced Machine DetectionOperational

Auth & Identity

  • Number InsightOperational
  • VerifyOperational
  • Verify V2Operational

Experiences

  • Vonage Conversational ConnectOperational
  • NLU APIOperational
  • Automatic Speech To TextOperational

Vonage Dashboard

  • Account Access & NotificationsOperational
  • Account Configuration & Feature AccessOperational
  • Creating An AccountOperational
  • Customer PortalOperational
  • Payments & BillingOperational
  • Reporting & DataOperational
  • OtherOperational

Global Connectivity

  • SMS North AmericaOperational
  • MMS North AmericaOperational
  • Voice North AmericaOperational
  • SMS EuropeOperational
  • Voice EuropeOperational
  • SMS APACDegraded
  • Voice APACOperational
  • SMS Latin AmericaOperational
  • Voice Latin AmericaOperational

SMS & Messages

  • SMSOperational
  • MMSOperational
  • SMPPOperational
  • CallbacksOperational
  • ShortcodesOperational
  • Phone NumbersOperational
  • 10 DLC PlatformOperational
  • Messages APIOperational
  • DispatchOperational

Meetings

  • Meetings ConnectionOperational
  • RecordingsOperational
  • ChatOperational
  • Dial InOperational

AI Studio

  • AI Studio AuthenticationOperational
  • AI Studio Builder UX/UIOperational
  • Campaign CreationOperational
  • ConnectorsOperational
  • Knowledge AIOperational
  • Reports EUOperational
  • Reports USOperational
  • Studio Messaging SessionsOperational
  • Studio Telephony SessionsOperational

Multiple Services Affected

  • Multiple Services AffectedOperational

Vonage API Support Platforms

  • Email SupportOperational
  • Live ChatOperational
  • Telephone SupportOperational
  • Help Center/Knowledge BaseOperational

Vonage Cloud Runtime

  • Deployment APIOperational
  • Marketplace APIOperational
  • Queue servicesOperational
  • DebugOperational
  • WorkspacesOperational
  • Persistence APIOperational
  • SchedulerOperational

Conversations for Salesforce

  • Conversations for SalesforceOperational

Network APIs

  • Network RegistryOperational
  • Identity InsightsOperational

Vonage Platform Management

  • Account APIsOperational
  • Alerts APIOperational
  • ApplicationsOperational
  • Audit APIOperational
  • Command Line Interface (CLI)Operational

Vonage incidents, last 90 days

  1. 2026-07-13: no record
  2. 2026-07-14: no record
  3. 2026-07-15: no record
  4. 2026-07-16: no record
  5. 2026-07-17: no record
  6. 2026-07-18: no record
  7. 2026-07-19: no record
  8. 2026-07-20: no record
  9. 2026-07-21: no record
  10. 2026-07-22: no record
  11. 2026-07-23: no record
  12. 2026-07-24: no record
  13. 2026-07-25: no record
  14. 2026-07-26: no record
  15. 2026-07-27: no record
  16. 2026-07-28: no record
  17. 2026-07-29: no record
  18. 2026-07-30: no record
  19. 2026-07-31: no record
  20. 2026-08-01: no record
  21. 2026-08-02: no record
  22. 2026-08-03: no record
  23. 2026-08-04: no record
  24. 2026-08-05: no record
  25. 2026-08-06: no record
  26. 2026-08-07: no record
  27. 2026-08-08: no record
  28. 2026-08-09: no record
  29. 2026-08-10: no record
  30. 2026-08-11: no record
  31. 2026-08-12: no record
  32. 2026-08-13: no record
  33. 2026-08-14: no record
  34. 2026-08-15: no record
  35. 2026-08-16: no record
  36. 2026-08-17: no record
  37. 2026-08-18: no record
  38. 2026-08-19: no record
  39. 2026-08-20: no record
  40. 2026-08-21: no record
  41. 2026-08-22: no record
  42. 2026-08-23: no record
  43. 2026-08-24: no record
  44. 2026-08-25: no record
  45. 2026-08-26: no record
  46. 2026-08-27: no record
  47. 2026-08-28: no record
  48. 2026-08-29: no record
  49. 2026-08-30: no record
  50. 2026-08-31: no record
  51. 2026-09-01: no record
  52. 2026-09-02: no record
  53. 2026-09-03: no record
  54. 2026-09-04: no record
  55. 2026-09-05: no record
  56. 2026-09-06: no record
  57. 2026-09-07: no record
  58. 2026-09-08: no record
  59. 2026-09-09: no record
  60. 2026-09-10: no record
  61. 2026-09-11: no record
  62. 2026-09-12: no record
  63. 2026-09-13: no record
  64. 2026-09-14: no record
  65. 2026-09-15: no record
  66. 2026-09-16: no record
  67. 2026-09-17: no record
  68. 2026-09-18: no record
  69. 2026-09-19: no record
  70. 2026-09-20: no record
  71. 2026-09-21: no record
  72. 2026-09-22: no record
  73. 2026-09-23: no record
  74. 2026-09-24: minor incident
  75. 2026-09-25: minor incident
  76. 2026-09-26: minor incident
  77. 2026-09-27: minor incident
  78. 2026-09-28: minor incident
  79. 2026-09-29: minor incident
  80. 2026-09-30: minor incident
  81. 2026-10-01: minor incident
  82. 2026-10-02: minor incident
  83. 2026-10-03: minor incident
  84. 2026-10-04: minor incident
  85. 2026-10-05: minor incident
  86. 2026-10-06: minor incident
  87. 2026-10-07: minor incident
  88. 2026-10-08: minor incident
  89. 2026-10-09: minor incident
  90. 2026-10-10: minor incident
2026-07-1317 of 17 days with an incidenttoday

Each bar is a day, coloured by the worst incident Vonage reported. It is their incident record, not a measurement of uptime.

Incidents
21
0 major or critical
Typical time to resolve
3 h 41 min
median
Nine in ten within
11 h 19 min
90th percentile
Longest
9 days
record since 2026-09-24
Started (UTC)IncidentImpactLasted
Verify API Service restorednoneunder a minute
Video: Issues impacting Media Connectionnoneunder a minute
Italy SMS - Delivery degradation towards Telekom Italia Networkminor3 h 41 min
USA SMS - Delivery degradation affecting SMS messages sent towards Verizon networkminor6 h 40 min
France Silent Authentication - Service degradation affecting Bouygues Telecomminor26 h 1 min
Video API - Media Session Service Degradation in EU West-1 Regionnoneunder a minute
USA MMS - Delivery degradation affecting MMS traffic towards AT&T operatorminor6 h 16 min
USA SMS & MMS - Delivery degradation affecting TFN & 10DLC traffic towards AT&T operatorminor4 h 55 min
Germany SMS - Delivery degradation towards 1&1 Germanyminor2 h 38 min
Nigeria SMS - Delivery Degradation affecting MTN Nigeria Networkminor11 h 19 min
Taiwan SMS - Delivery degradation of Domestic Pre-Registered Brandsminor4 h 39 min
Video API Service Issue — US West Regionnoneunder a minute
USA SMS - Delivery Degradation affecting T-mobile Network through a subset of 10DLC numbersminor6 h 16 min
Spain SMS - Delivery Degradation affecting DiGi Spain Network (21422)minor2 h 26 min
Service Issue (Billing) in Platformnoneunder a minute
Advanced Machine Detection Issuesnoneunder a minute
Voice API - WebRTC Service Degradation | APAC Regionminor4 h 40 min
USA SMS - Delivery degradation affecting Short Code traffic towards AT&T operatorminor4 h 30 min
Issues impacting Customer Dashboard Aggregations for Verify v2minor1 h 7 min
Sweden and Lithuania Voice - Degradation impacting Calls towards all networks affecting subset of Vonage Long Virtual Numbersminor9 days
Sweden SMS & Voice - Degradation call and sms towards all network affecting Long Virtual Numbersnoneunder a minute

Get alerted when Vonage goes down

No account. One email when Vonage reports an incident, one when it is over. You confirm the address first, and every email has a one-click unsubscribe.

Or follow the RSS feed. On UpButler? Add Vonage as a dependency to route it to Slack, Teams or a webhook.

Status badge

Show Vonage's current status in a README or an internal wiki. It updates by itself.

Vonage status badge

[![Vonage status](https://upbutler.com/status/vonage/badge.svg)](https://upbutler.com/status/vonage)

Tell your outage from Vonage's

Declare that your project depends on Vonage. When one of your monitors fails while Vonage has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start freeHow it works
upbutler.yaml
# upbutler.yaml
dependencies:
  - vonage
Ask before you retry
curl -s https://upbutler.com/status/vonage/status.agent.json
status.agent.json (live)
{
  "schema": "upbutler.upstream-status/v1",
  "service": "vonage",
  "verdict": "proceed",
  "status": "degraded",
  "reason": "China SMS - Delivery degradation of Pre-Registered brands",
  "retryAfterSec": null,
  "incident": {
    "title": "China SMS - Delivery degradation of Pre-Registered brands",
    "url": "https://vonageapi.statuspage.io/incidents/scq7gpq29w1l"
  },
  "probe": null
}

Questions

Is Vonage down right now?
Partly. As of 2026-10-10 07:16 UTC, Vonage is having issues, with an open incident: "China SMS - Delivery degradation of Pre-Registered brands". This page reads the status again every 3 minutes.
How long do Vonage outages usually last?
Of the 21 incidents Vonage reported in the last 90 days, half were resolved within 3 h 41 min and nine in ten within 11 h 19 min; the longest took 9 days. These are the provider's own start and end times.
Where does this status come from?
From Vonage's own status page API at https://vonageapi.statuspage.io. UpButler reads it once for everyone (not once per visitor) every 3 minutes with conditional requests, and shows it unchanged: incident titles and component names are Vonage's words.
Can I get an alert when Vonage goes down?
Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Vonage reports an incident and one when it is over. There is also an RSS feed at https://upbutler.com/status/vonage/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.
How can my agent or app check Vonage status?
Fetch https://upbutler.com/status/vonage/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"vonage"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Vonage's?
Add "vonage" to the dependencies of your UpButler workspace. When one of your monitors fails while Vonage has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Also check

UpButler is not affiliated with Vonage. Status and incident text belong to Vonage and are read from their public status source; the probe result is UpButler's own measurement.