Loading status…
Loading status…
Twilio status · AI & APIs · checked (6s ago)
Partly — Twilio is up but running slower than usual (Partially Degraded Service).
According to Twilio's official status page, Twilio was reporting “Partially Degraded Service” when isuptime last checked at . Over the last 30 days, Twilio's feed reported no outage in 100.00% of our checks.
isuptime cannot fix Twilio, and neither can you. These are the things that are actually worth doing until it comes back.
Everything above is read from Twilio's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Twilio in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Twilio provides programmable messaging, voice, video and verification APIs — SMS and WhatsApp delivery, phone calls, and the two-factor codes a great many products depend on. A Twilio incident usually shows up in someone else's product as “the verification code never arrived”.
Twilio's status page is broken out by product and by region, and messaging is further split by channel and by geography, because SMS delivery depends on local carrier routes. That detail is important: SMS to one country can be failing while everything else on the account is healthy, and carrier-level delays are frequently posted as degraded rather than as an outage.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Twilio's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Twilio was down.
8 other services isuptime tracks were also reporting a problem as of the same check, 6s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Twilio's status endpoint.
Twilio has published 50 incidents in the last 12 months, the 20 most recent shown here. Only what Twilio posted itself — not every problem users hit.
identified · Sep 23, 03:02 PM (2h ago)
resolved · Sep 23, 12:53 PM (4h ago)
identified · Sep 23, 10:58 AM (6h ago)
resolved · Sep 23, 06:32 AM (10h ago)
resolved · Sep 22, 08:44 PM (20h ago)
resolved · Sep 22, 08:27 PM (20h ago)
resolved · Sep 22, 07:23 PM (22h ago)
resolved · Sep 22, 06:20 PM (23h ago)
resolved · Sep 22, 09:19 AM (1d ago)
resolved · Sep 22, 08:50 AM (1d ago)
resolved · Sep 22, 06:55 AM (1d ago)
resolved · Sep 22, 06:19 AM (1d ago)
resolved · Sep 22, 04:20 AM (1d ago)
resolved · Sep 21, 11:54 PM (1d ago)
resolved · Sep 21, 05:25 PM (1d ago)
resolved · Sep 21, 02:45 PM (2d ago)
resolved · Sep 21, 01:42 PM (2d ago)
resolved · Sep 21, 09:51 AM (2d ago)
identified · Sep 21, 06:10 AM (2d ago)
resolved · Sep 20, 10:28 PM (2d ago)
Undelivered SMS is more often carrier filtering than a Twilio outage — check the message status and error code in the Twilio console, which will tell you whether the carrier rejected it. Unregistered A2P 10DLC campaigns, unverified sender IDs and blocked shortcodes all cause silent delivery failure. A depleted account balance stops sending without any platform incident.