Twilio statusLiveFetched seconds agoSource: status.twilio.com
Is Twilio down?
Live status check · Degraded performance
Partially Degraded Service
Live status pulled from status.twilio.com, cached and revalidated every 60 seconds. Below: the components that can break, what to do during an incident, and how to keep your scheduled jobs running independently.
About Twilio status
Twilio is the largest programmable communications platform, covering SMS, voice, WhatsApp Business, and email (via the SendGrid acquisition). Incidents are almost always scoped to a single channel or region rather than the whole platform.
Components and surfaces that can break
- Surface 01
Messaging (SMS, MMS, WhatsApp Business, Conversations).
- Surface 02
Voice (PSTN trunking, SIP, Elastic SIP, Programmable Voice).
- Surface 03
Verify and Authy 2FA (one-time passcodes, push, TOTP).
Recent Twilio incidents
Twilio maintains a public incident history. Read the latest entries to see whether you're hitting a known issue, and look at the post-mortems for context on how long similar incidents typically take to clear.
What to do if Twilio is actually down
Read status per channel and per region
status.twilio.com splits incidents by channel (Messaging, Voice, Verify) and by region (US1, IE1, AU1, etc.). An SMS outage in a single country code does not affect voice or other regions; confirm the matching row before you fail anything over.
Use a Messaging Service if you want queueing
Twilio queues outbound SMS internally for brief degradations, but customer-visible queueing and smart retries only kick in when you send through a Messaging Service rather than calling POST /Messages with a raw From number. Switch your sender to a Messaging Service if reliability during incidents matters.
Have a backup factor for time-sensitive 2FA
If you only deliver one-time codes over Twilio SMS, a regional carrier blip can lock users out of your product. Enable a second factor in Twilio Verify (TOTP authenticator app or email) so users have a way in when SMS is degraded.
Keep firing through the incident
Schedule your own Twilio health check with Crontap
Scheduled SMS reminders, daily account-status texts, monthly on-call digest pings. Crontap fires the handler that calls Twilio's Messages API on the cadence you set; retries on 5xx and stores the response body so a failed send surfaces in the alert email.
External HTTP cron hits your endpoint on the cadence you pick, stores every response, and emails you the moment a run fails. Pro schedules down to 1 minute; $3.25/mo annual flat for unlimited jobs.
Go deeper
Twilio status: FAQ
- Where can I see the official Twilio status?
- status.twilio.com publishes component status per product (Messaging, Voice, Verify, Email API, Studio, Flex) and per region. The history page and history.atom feed cover past incidents with timestamps and post-mortems.
- Why did my Twilio SMS arrive late but not bounce?
- Carrier networks queue messages during local congestion or filtering events, so Twilio reports the message as 'sent' (accepted by the carrier) even when the recipient sees it minutes later. The Twilio status page often flags this as 'delivery delays' on a specific country code rather than a hard outage.
- Does Twilio retry sends that failed during an outage?
- If your POST /Messages call returned an error, the message was never accepted and Twilio will not retry it for you. If you use a Messaging Service, Twilio handles smart retries against carrier failures, but request-level errors are still your responsibility to retry. Crontap retries 5xx responses on your own endpoint, which is the layer that calls Twilio.