Vendor Status Dashboard

Live check

Is Twilio down right now?

Checking Twilio’s status page…

Fetched live from status.twilio.com by your own browser — we never proxy, cache, or fake it.

While you wait: the Twilio incident checklist

  1. Scope by product and geography. SMS, Voice, Verify and WhatsApp are separate components, and messaging incidents are often country- or carrier-specific. status.twilio.com breaks this down — read past the headline before deciding impact.
  2. Protect logins first. If OTPs ride Twilio (Verify or raw SMS), users can't sign in. Enable the fallbacks now — TOTP, email codes, backup codes — or consider temporarily extending session lifetimes so fewer people hit the login wall.
  3. Make webhook handlers boring. Status callbacks and inbound webhooks may arrive late, duplicated and out of order during recovery. Idempotent handlers with out-of-order tolerance are what save you here.
  4. Distinguish queued from failed. Accepted-but-undelivered messages may be delayed rather than lost. Don't blind-resend everything — reconcile against delivery receipts first, or you'll double-message users when the queue flushes.
  5. Check your own paging path. If on-call pages go out via Twilio SMS or Voice — directly or through your paging provider — confirm the provider's non-SMS channels (push, email) are enabled for the rotation.

What breaks when Twilio has issues

Twilio incidents surface as user-facing authentication and communication failures: OTP codes that never arrive (login lockouts and a support-ticket flood), missing transactional notifications, dead IVR and callback flows on Voice, and silent SMS/WhatsApp sends. Recovery brings its own wave — delayed messages flushing to users hours late and webhook retries hammering your endpoints. And if your paging pipeline uses SMS as its only channel, the incident can mute your own on-call alerts.

FAQ

SMS is delayed — is it Twilio or the carrier?

Either. Twilio's status page splits messaging by product and region, but downstream carrier degradation doesn't always show there. Delays across multiple carriers point at Twilio; one carrier lagging points downstream.

What happens to messages sent mid-outage?

It depends where they failed. API errors at submit time mean the message wasn't sent — your call whether to retry. Accepted-but-queued messages are generally delivered late rather than dropped, so reconcile with delivery receipts before resending.

How do I keep logins working during an SMS outage?

Offer a second factor that isn't SMS: TOTP, email OTP, backup codes, or passkeys. If none of those exist yet, weigh temporarily relaxing re-authentication against your threat model.

Is SendGrid email on this status page?

No — SendGrid, Twilio's email product, publishes separately at status.sendgrid.com. If you use both, check both.

Get pinged in your toolbar the moment Twilio’s status changes

Vendor Status Dashboard is a Chrome extension for on-call engineers: Twilio and every other vendor you depend on, one badge, answer in five seconds. Free for 5 vendors, no account.

Join the waitlist — launching soon

Also on your stack?

Not affiliated with Twilio. Status data comes from their public status page.