Twilio logged eight separate incidents on 2 November 2026, touching SMS routes in North America, Europe and Latin America, voice calls in the Philippines, Silent Network Auth in Indonesia and account billing. One of these, the Philippines voice call failures, was still open at the last update Twilio published. The faults sat inside Twilio's own network and routing, not in your integration.
Started
00:51 UTC
Duration
Lasted 6h 35m
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, Latin America, Billing, SMS, Europe, Verify Silent Network Auth, Voice, APAC, SMS Short Code, North America
What happened?
Twilio's status page recorded eight incidents starting at 00:51 UTC and running through the day, with 59 status updates posted in total. The first was SMS delivery delays from a subset of Twilio short codes to Google Voice subscribers in the United States, opened at 00:51 and resolved by 07:24, a run of 6h 35m. At 05:41 Twilio opened a voice call failure affecting a subset of its Philippines phone numbers across multiple networks there. That one went through repeated identified and monitoring updates all day, with Twilio stretching its promised update window from one hour out to 24 hours at points, and it remained unresolved, making it the longest-running item on the page. A separate case hit Silent Network Authentication on XL Axiata in Indonesia from 06:54, lasting 13h 27m before Twilio marked it resolved at 20:21. SMS delays to T-Mobile and O2 in the Czech Republic ran for 2h 54m, and delays and failures on Alphanumeric Sender IDs to T-Mobile Austria ran for 5h 17m. A billing problem, incorrect balances shown on customer accounts, started at 16:37 and was not resolved until 01:26 the next day, a span of 32h 51m. Two further SMS problems hit Puerto Rico: delivery receipt delays to Liberty lasting 7h 44m, and delivery delays and failures to Claro lasting 7h 23m. Six components in total were affected across the day: SMS Short Code North America, Voice APAC, Verify Silent Network Auth, SMS Europe, Billing and SMS Latin America. No user reports were filed in this window. Twilio's own updates are the only record of what happened, and each incident's account comes from what the company chose to publish.
Learning
UptimeRobot's own probes against Twilio's API, checked every 60 seconds from the EU and North America, stayed at 100% uptime across the last 24 hours, 7 days and 30 days, with no outage registered against this incident. That is not a contradiction. Twilio's problems on this day sat in carrier routing and account billing logic, specific SMS routes to specific networks, voice calls on specific numbers in the Philippines, balances on specific accounts, none of which shows up as a failed API health check. A generic uptime probe hits an endpoint and gets a clean response even while messages are failing to reach a carrier three hops downstream, or a customer's dashboard shows the wrong number. This is the shape to watch for in your own product: your API calls to Twilio succeed, your monitoring is green, and your users still can't get an SMS through or see a wrong balance. Your own monitoring covers your half of that chain. UptimeRobot now watches the provider's half too, so next time something breaks you know which side it is without guessing.