Is Vonage Down? Complete Status Check Guide + Quick Fixes

Vonage calls not connecting?
API requests failing?
SMS messages not delivering?

TL;DR: If you think Vonage is down, check the official Vonage status page and a live monitor first.
If both show operational, the issue is likely local (network, API credentials, account settings, or carrier issues).
This guide covers quick checks, fixes, and when to worry if Vonage is not working.

Quick Check: Is Vonage Actually Down?

Don't assume it's Vonage.
Most "Vonage down" reports are caused by network issues, expired API credentials, carrier delivery problems, or account configuration changes.

60-second triage

1. Check the Vonage status page.
2. Test a simple API call (e.g., account balance).
3. Try calling from a different device or network.
4. Check if the issue is voice, SMS, or API-specific.

Quick decision tree

Status page operational + only you affected → Local/account issue
Status page operational + one product down → Product-specific incident
Status page degraded + widespread reports → Vonage platform incident

Keywords people search

• "Vonage down"
• "Vonage status"
• "Vonage not working"
• "is Vonage down today"

Official Sources

Vonage Status Page (Primary)

Vonage Status:
🔗 vonageapi.statuspage.io (API platform)
🔗 status.vonage.com (Business Communications)

What to look for:

• ✅ All Systems Operational
• ⚠️ Degraded Performance
• 🔴 Major Outage

Common components listed:

• Voice API
• SMS API
• Verify API (2FA)
• Video API (Tokbox)
• Messages API
• Voice (Business)
• UCaaS Platform
• Contact Center
• Admin Portal
• Number Management

API Status Check (Independent Monitor)

Live monitoring:
🔗 apistatuscheck.com/api/vonage

Live "Is Vonage Down" page

🔗 apistatuscheck.com/is-vonage-down

Status notifications

• Email/SMS alerts from the status page
• RSS feeds for incident changes
• Follow @VonageDev on Twitter/X

Third-party tools

DownDetector

🔗 downdetector.com/status/vonage

IsItDownRightNow

🔗 isitdownrightnow.com/vonage.com.html

Twitter/X search

🔗 Search "Vonage down" on Twitter/X

Community + forums

• Vonage Developer Community
• Vonage API GitHub issues
• r/VoIP on Reddit
• UCaaS forums

Common Issues

Issue: Voice API calls failing

Symptoms:

• Outbound calls not connecting
• Call quality degraded (choppy, one-way audio)
• Webhook callbacks not received
• SIP trunk registration failing

Likely causes:

• Voice API service degradation
• Carrier interconnect issues
• Network/firewall blocking RTP traffic
• SIP credentials expired

What to check:

• Status page for Voice API
• Test with a different destination number
• Check webhook URL accessibility
• Verify SIP credentials and trunk config

Issue: SMS not delivering

Symptoms:

• Messages stuck in "Submitted" status
• Delivery receipts showing failures
• International SMS blocked
• DLR callbacks not arriving

Likely causes:

• SMS API degradation
• Carrier filtering or blocking
• Sender ID not approved for destination country
• Account balance insufficient

What to check:

• Status page for SMS API
• Check delivery receipts via API
• Verify sender ID/number registration
• Test with a different destination carrier

Issue: Verify API (2FA) failures

Symptoms:

• OTP codes not arriving
• Verify requests timing out
• "Invalid request" errors
• Rate limit errors

Likely causes:

• Verify API degradation
• SMS delivery issues downstream
• Rate limiting on verification requests
• Country-specific restrictions

What to check:

• Status page for Verify API
• Check if SMS delivery works independently
• Review rate limit headers
• Test with a different phone number

Issue: Video API (Tokbox) problems

Symptoms:

• Video sessions not connecting
• Audio/video quality poor
• Screen sharing fails
• Session creation API errors

Likely causes:

• Video API service degradation
• Browser compatibility issues
• WebRTC firewall blocks
• TURN/STUN server issues

What to check:

• Status page for Video API
• Test with Vonage's video playground
• Check browser console for WebRTC errors
• Verify firewall allows UDP traffic

Issue: Business phone service down

Symptoms:

• Desk phones not registering
• Mobile app can't connect
• Voicemail not working
• Call queues not routing

Likely causes:

• UCaaS platform degradation
• SIP registration issues
• Admin portal changes
• Regional carrier problems

What to check:

• Status page for Business Communications
• Test from mobile app vs. desk phone
• Check admin portal for changes
• Try a different network

Issue: API authentication failures

Symptoms:

• 401 Unauthorized errors
• API key rejected
• JWT token invalid
• Application ID not found

Likely causes:

• API key/secret rotated
• Application deleted or misconfigured
• Auth service degradation
• Rate limits exceeded

What to check:

• Verify API credentials in dashboard
• Generate a new API key/secret
• Check application settings
• Review API response headers

Quick Fixes

Fix #1: Test API connectivity

# Check account balance (simple auth test)
curl -u API_KEY:API_SECRET \
  https://rest.nexmo.com/account/get-balance

# Test SMS
curl -X POST https://rest.nexmo.com/sms/json \
  -d "api_key=KEY&api_secret=SECRET&from=TEST&to=NUMBER&text=test"

Fix #3: Verify webhook accessibility

# Test if your webhook URL is reachable
curl -I https://your-app.com/webhooks/vonage

If webhook fails: Your server may be down, not Vonage.

---

Fix #4: Test from a different network

Why: Corporate firewalls can block VoIP/SIP traffic.

Try:

• Mobile hotspot
• Home network
• Disable VPN

---

Fix #5: Check number capabilities

1. Verify the number is active in your dashboard
2. Confirm SMS/Voice capabilities enabled
3. Check country-specific registration requirements
4. Verify compliance with local regulations (10DLC, A2P)

---

Fix #6: Clear SIP registration

For desk phones:

1. Reboot the phone
2. Check SIP trunk credentials
3. Verify registration server address
4. Test with a softphone as backup

---

Fix #7: Review rate limits

Vonage API rate limits:

• SMS: varies by account type
• Voice: concurrent call limits
• Verify: request throttling

Check response headers for remaining quota.

---

Fix #8: Flush DNS

Mac:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Windows:

ipconfig /flushdns

History of outages

Where to find incident history

• vonageapi.statuspage.io (API)
• status.vonage.com (Business)

Typical causes

• Carrier interconnect failures
• SIP infrastructure issues
• API gateway overload
• Regional routing problems
• Certificate or auth service failures

What to document

• Time of impact and affected services
• Voice vs. SMS vs. API isolation
• Geographic scope
• Number of affected users/calls

When to worry

Signs it's a real outage

• Status page shows degradation
• Multiple customers affected across carriers
• API calls consistently returning 5xx
• Both voice and SMS failing simultaneously

Signs it's local

• Only one number or route affected
• Works on a different network
• Only one API product failing
• Carrier-specific delivery issues

Escalation checklist

1. Check both status pages (API and Business)
2. Test from multiple networks
3. Verify API credentials are valid
4. Contact Vonage support with timestamps and error codes

FAQ

Is Vonage down right now?

Check vonageapi.statuspage.io and apistatuscheck.com/api/vonage.

Why are my Vonage SMS not delivering?

Check SMS API status, verify sender ID registration, confirm account balance, and test with a different carrier.

Can Vonage Voice be down while SMS works?

Yes. Voice and SMS are separate services that can fail independently.

How do I check Vonage status quickly?

Open the status pages and apistatuscheck.com/is-vonage-down.

How can I monitor Vonage automatically?

Use apistatuscheck.com/api/vonage for uptime alerts via RSS, Slack, Discord, or email.

Related Resources

• API Status Check — Vonage Monitoring
• Official Vonage API Status