On 1 October, Twilio logged six separate incidents affecting SMS, voice and campaign registration across Brazil, Spain, the US, APAC and India. The longest, a voice failure to DigiMobil subscribers in Spain, ran 12 hours 14 minutes. All six were carrier or route specific faults on Twilio's side, not a problem with your own integration.
Started
00:26 UTC
Duration
Lasted 7h 24m
Source
IsDown
Next time
Twilio is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: SMS, APAC, Trust Hub, Voice, Europe, SMS Short Code, North America, SMS, Europe, SMS, Latin America
What happened?
Twilio's status page recorded six incidents starting at 00:26 UTC and running through the day into the next. The first was SMS delivery delays from Twilio to Algar Telecom (CTBC) subscribers in Brazil, lasting 7 hours 24 minutes before resolution at 07:35. Within an hour of that closing, a second incident opened: SMS delivery delays and failures to DigiMobil (Movistar) subscribers in Spain, running 4 hours 54 minutes. Overlapping with that, a third incident hit SMS delivery receipts from a subset of Twilio Short Codes to multiple US networks, where Twilio noted that message delivery could still succeed even though receipts were delayed, resolved after 3 hours 12 minutes. The longest incident of the day started at 10:40: voice call failures and post dial delay from Twilio phone numbers to DigiMobil subscribers in Spain, which took 12 hours 14 minutes and three separate "monitoring" updates before Twilio called it resolved at 22:51. A fifth incident affected A2P campaign registration generally, with Twilio's own monitoring flagging delays in campaign submissions, running almost 5 hours. The sixth started late in the day, at 23:01, with SMS delivery delays from a subset of Twilio phone numbers to Jio subscribers in India, lasting 7 hours 41 minutes. Across all six, Twilio's updates followed the same pattern: investigating, identified, monitoring, resolved, with no root cause published beyond naming the affected carrier or route. No user reports were filed during the window on this page. In total, 33 updates were posted across the six incidents, and components affected spanned SMS in Latin America, Europe and APAC, SMS Short Code in North America, Voice in Europe, and Trust Hub.
Learning
UptimeRobot's own probes, which check Twilio's API from EU and North America, stayed at 100% uptime across 24 hours, 7 days and 30 days, and did not register any of these six incidents. That is not a contradiction. Every incident on this page was scoped to specific carriers and specific routes, Algar in Brazil, DigiMobil in Spain, Jio in India, a subset of US short codes, which is exactly the kind of fault that lives between Twilio's platform and a downstream telecom network rather than in the API endpoint itself. An external check hitting the API can get a clean 200 response while messages or calls to one named carrier still sit delayed or fail. This is the shape to watch for in your own product: delivery or call quality problems reported by users in one country or on one network, while your own health checks and Twilio's dashboard both look fine. Over the past 90 days Twilio has logged 528 such incidents with a median duration of 5 hours 20 minutes, so this pattern recurs often enough to plan for. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
