Is Twilio Down? How to Tell and What to Do
Twilio powers the SMS, voice, WhatsApp, email, and 2FA infrastructure for hundreds of thousands of applications. When it goes down, the symptoms look like your own code broke — users can't verify phone numbers, receive OTPs, or get notified — but the root cause is upstream.
The fastest way to know: Statusfield monitors Twilio continuously and alerts you within minutes. Without monitoring, you're waiting for support tickets to pile up.
Know when Twilio is down — before your team does
Statusfield monitors Twilio alongside your other critical tools and sends real-time alerts when anything degrades. Every plan starts with a free trial — no credit card required.
Every plan: 30-day free trial — no card needed
Common Signs of a Twilio Outage
| Symptom | What's likely happening |
|---|---|
| SMS messages not delivering | Twilio's SMS carrier routing is degraded |
| Voice calls dropping or failing | Voice infrastructure or PSTN connectivity issue |
| 2FA / OTP codes never arrive | Programmable SMS or email delivery impacted |
| WhatsApp messages stuck as "sent" but not delivered | WhatsApp Business API degradation |
21408 or 30003 error codes in API responses | Twilio-side delivery failures |
| Webhook callbacks not firing | Twilio's webhook delivery service degraded |
| HTTP 503 from the Twilio API | Service temporarily unavailable |
How to Confirm It's Twilio, Not You
Before opening a support ticket or rolling back your deployment, rule out your own infrastructure:
1. Check your API error codes first
Twilio surfaces specific error codes when delivery fails on their side:
| Error Code | Meaning |
|---|---|
30003 | Unreachable destination — carrier-level issue |
30005 | Unknown destination handset — valid but undeliverable |
30006 | Landline or unreachable carrier |
21408 | Permission not enabled — account configuration (not outage) |
21211 | Invalid 'To' phone number format |
53000 | SDK-level connection error — likely a Twilio service issue |
53001 | Signaling connection disconnected — Voice SDK degraded |
If you're seeing 30003 or 53000–53xxx errors across multiple requests from different phone numbers, it's an infrastructure issue, not a data problem.
2. Test with a different medium
Send a test message to a number you control. If it fails across SMS and WhatsApp, the issue is almost certainly platform-wide, not carrier-specific.
3. Check your own webhook receipt
If Twilio webhooks are not arriving (status callbacks, delivery receipts), that's a distinct Twilio system from SMS delivery — worth isolating.
4. Look at your logs across regions
Twilio outages often affect specific regions or carrier partnerships before spreading globally. If your EU traffic is failing but US is fine, the impact may be partial.
The Problem With Vendor Status Pages
Most developers check status.twilio.com during an incident. The issue: Twilio's status page is updated manually by their SRE team, often 15–30 minutes after the incident begins — after users have already noticed and support tickets have started coming in.
You should not be waiting on a vendor to tell you something is wrong. Your users will tell you first, and that's the worst possible early warning system for a production application.
Statusfield monitors Twilio around the clock and fires alerts the moment something degrades — before your support queue fills up.
Don't wait on Twilio's status page
Statusfield alerts you the moment Twilio degrades — no need to refresh a status page or wait for a support ticket. Every plan starts with a free trial — no credit card required.
Every plan: 30-day free trial — no card needed
What to Do During a Twilio Outage
Immediate (first 5 minutes)
- Confirm it's Twilio — check your error codes against the table above and verify it's not a misconfiguration on your end
- Enable a fallback path — if you have a secondary SMS provider configured, route new requests through it
- Freeze retry loops — exponential backoff against a degraded Twilio API can burn through your message quota and delay recovery
- Set your internal status — let your team know you're investigating; don't wait to have a root cause before communicating
Communication (first 15 minutes)
- Post a brief update to any internal monitoring channels ("Investigating: SMS delivery delays, likely upstream")
- If you expose a status page to customers, mark the affected service as degraded
- Hold off on customer-facing notifications until you've confirmed scope
Recovery
- Once Twilio resolves the incident, re-queue any failed messages with priority
- Review retry logic — failed messages from a Twilio outage may need to be replayed differently from local failures
- Document the incident timeline for your team
Twilio Services and What Each Outage Looks Like
Twilio is not a single service — it's a platform with distinct components that can degrade independently:
| Service | Impact when down |
|---|---|
| Programmable SMS | OTP codes, transactional SMS, marketing messages fail |
| Programmable Voice | Inbound/outbound calls fail or drop |
| Verify API | Phone verification and 2FA completely blocked |
| WhatsApp Business API | WhatsApp messages not delivered |
| Twilio Email (SendGrid) | Transactional email not delivered |
| TaskRouter | Call center / contact center routing breaks |
| Twilio Sync | Real-time data sync for IoT and apps fails |
| Authy / TOTP | Authenticator-based 2FA may be impacted |
A partial outage affecting only Verify (2FA) can be just as disruptive as a full SMS outage — especially if you require phone verification at signup.
Why DIY Monitoring Always Fails for Twilio
It seems simple enough: poll the Twilio API every minute, check the response time, alert if it's slow. Here's why it doesn't work:
- Response time ≠ delivery success — the API can return 200 but messages still fail to deliver to end users
- No carrier visibility — Twilio's routing goes through carrier partnerships you have no visibility into; your health check can't see that
- The Verify API is separate from SMS — a check against one doesn't cover the other
- Maintenance windows — Twilio occasionally performs maintenance that degrades a specific region or service; your naive ping won't distinguish that from a full outage
Real Twilio monitoring requires checking actual delivery success rates, not just HTTP responses. That's what Statusfield does.
Monitor Twilio Before Your Users Notice
Statusfield monitors Twilio and 1,700+ other services continuously. When something degrades, you get alerted — not your users.
3 monitors, 10 alerts/month, no credit card required.
Monitor Twilio before the next outage costs you
Statusfield watches Twilio and 1,700+ other services continuously, alerting you the moment something degrades. Every plan starts with a free trial — no credit card required.
Every plan: 30-day free trial — no card needed
FAQ
Is Twilio down right now?
Check Statusfield for real-time Twilio status. If you're seeing SMS delivery failures or 2FA codes not arriving, Statusfield will tell you if it's a platform issue or something on your end.
Why are my Twilio messages not being delivered?
Delivery failures usually come down to four causes: a Twilio platform outage (look for error codes 30003 or 53xxx), a carrier-routing problem for a specific region, a misconfigured sending number, or a destination number on a blocklist. Cross-reference error codes from the table above to narrow it down.
How long do Twilio outages last?
Most Twilio outages are resolved within 30 minutes to 2 hours. Carrier-routing incidents that affect specific regions can last longer. Regional degradations are more common than full platform outages.
What's the difference between a Twilio outage and a carrier issue?
A Twilio outage affects all traffic across all carriers. A carrier issue hits only messages routed through a specific carrier, typically in one region. If some SMS messages are succeeding while others fail, you're likely looking at a carrier issue rather than a platform-wide incident.
How do I get alerted when Twilio goes down?
Statusfield monitors Twilio continuously and fires alerts the moment it detects a degradation — before your support queue fills up. Every plan starts with a free trial — no credit card required.
Know the moment a tool you depend on goes down
Statusfield watches 7,000+ services your business depends on and alerts you the moment they break.
Every plan: 30-day free trial — no card needed
Related Articles
Is Facebook Down Right Now? How to Know Before Everyone Else
Facebook outages affect billions of users but vendor status pages lag 15-30 minutes. Here's how to diagnose a Facebook outage fast and get alerted before the complaints roll in.
Is the Apple App Store Down? How to Tell and What to Do
When the Apple App Store goes down, downloads stall, in-app purchases fail, and app updates get stuck — often silently. Here's how to diagnose an App Store outage fast.
Is Amazon CloudFront Down? How to Tell and What to Do
When Amazon CloudFront degrades, your CDN-delivered assets stall, API responses slow, and users see errors — before AWS posts anything. Here's how to diagnose a CloudFront outage fast.