Skip to main content
Vonage logo

Is Vonage Down?

No — Vonage is up

Reachable from all 8 checked regions

Average response time: 305ms

Last checked · checks run every 6 hours

Official status page: https://uc.vonagestatus.com

Vonage uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
236ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 20 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

20-day clean streak
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: no data
Aug 27: no data
Aug 28: no data
Aug 29: no data
Aug 30: no data
Aug 31: no data
Sep 1: 100.00% uptime, 16 checks
Sep 2: 100.00% uptime, 32 checks
Sep 3: 100.00% uptime, 16 checks
Sep 4: 100.00% uptime, 23 checks
Sep 5: 100.00% uptime, 28 checks
Sep 6: 100.00% uptime, 16 checks
Sep 7: 100.00% uptime, 32 checks
Sep 8: 100.00% uptime, 36 checks
Sep 9: 100.00% uptime, 32 checks
Sep 10: 100.00% uptime, 32 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 32 checks
Sep 13: 100.00% uptime, 23 checks
Sep 14: 100.00% uptime, 31 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 23 checks
Sep 17: 100.00% uptime, 31 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 24 checks
Aug 22 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
265ms
DNS 60ms TCP 1ms TLS 7ms TTFB 264ms
arn
402ms
DNS 169ms TCP 1ms TLS 7ms TTFB 401ms
bom
637ms
DNS 176ms TCP 2ms TLS 8ms TTFB 637ms
cdg
166ms
DNS 36ms TCP 1ms TLS 6ms TTFB 166ms
dfw
270ms
DNS 137ms TCP 1ms TLS 4ms TTFB 270ms
ewr
225ms
DNS 164ms TCP 2ms TLS 6ms TTFB 224ms
fra
188ms
DNS 59ms TCP 1ms TLS 6ms TTFB 187ms
yyz
293ms
DNS 182ms TCP 8ms TLS 13ms TTFB 293ms

What Vonage does

Vonage sells several different products under one brand. Vonage Business Communications is a hosted phone system: desk phones, softphones, call queues and voicemail for small and mid-sized companies. Vonage API, formerly Nexmo, is a developer platform for programmable voice, SMS and verification. Vonage Contact Centre is a separate agent product again. Each runs on its own infrastructure and publishes its own status page.

What an outage looks like

Handsets show as unregistered and stop ringing, or calls connect but drop and break up. Vonage reports Registration, Inbound Call Completion, Outbound Call Completion and Voice Quality as four separate components, so the admin portal and desktop app can look completely normal while no call actually completes. SMS, fax and voicemail are separate components again and can fail on their own.

What to do about it

Decide which Vonage you use first. For the phone system, uc.vonagestatus.com covers the Admin Portal, desktop and mobile apps, Vonage Meetings, call queues and the call-completion components. Programmable voice and SMS publish at vonageapi.statuspage.io, and the contact centre product publishes separately again at vcc.statuspage.io. Reading the wrong one is the most common way people conclude Vonage is fine when their service is not.

Is it down for everyone, or just you?

If this page says Vonage is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Vonage outage FAQ

Which Vonage status page should I be reading?
If your company bought a phone system with desk phones, extensions and call queues, read uc.vonagestatus.com. If a developer at your company sends SMS or places calls from code, that is the Vonage API platform at vonageapi.statuspage.io. If your agents work queues in Vonage Contact Centre, that is a third page again at vcc.statuspage.io. The three run on different infrastructure, so one can be operational while another is not.
My phones show no service but the Vonage portal works. Is it down?
Possibly, and this is the normal shape of a Vonage incident. Registration is its own component, separate from the Admin Portal. When registration fails, handsets cannot attach to the platform and appear dead while the web portal and its settings pages load perfectly. Check the Registration and call-completion entries rather than judging by whether the portal opens.
Can I make calls but not receive them, or the other way round?
Yes. Vonage tracks Inbound Call Completion and Outbound Call Completion as two separate components, so one direction can fail while the other works. If customers say they cannot reach you but your outbound calls connect, that is a recognised split rather than a misconfiguration on your end. Check both entries before changing any routing.
Does a Vonage outage affect the Microsoft Teams integration?
It can, independently of the rest. Vonage lists Microsoft Teams, the Vonage Integration Suite and other integrations as their own components. A Teams calling integration can be interrupted while native Vonage handsets are unaffected, so users inside Teams report an outage that desk-phone users never notice.
Do voicemails and faxes survive an outage?
Vonage does not publish retention or retry behaviour for voicemail and fax on its status page, so we will not claim messages are held. Voicemail, Fax and Call Forwarding are listed as separate components, which means they can fail while calls work. After an incident, check voicemail directly rather than assuming notification emails arrived.

How we measure this

  • We request Vonage's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Vonage publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Vonage goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required