On 2 October 2026 Twilio ran three separate incidents touching SMS delivery in Europe and Silent Network Auth verification in the United States. The longest resolved stretch ran 6 hours 39 minutes, and one incident was still open at 12:40 UTC, the last update Twilio published. All three were faults on Twilio's side, not yours.
Started
04:42 UTC
Duration
Lasted 6h 39m
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, Europe, Verify Silent Network Auth
What happened?
Twilio logged three incidents starting at 04:42, 06:56 and 09:35 UTC on 2 October 2026. The first affected SMS delivery from a subset of Twilio phone numbers to Vodafone subscribers in the Netherlands, running 6 hours 39 minutes before Twilio marked it resolved at 11:20 UTC. The second hit Silent Network Authentication for API transactions on AT&T in the United States, with Twilio noting that failed SNA checks could fail over to secondary methods like SMS OTP. That one moved to monitoring at 10:40 UTC but had no resolved update filed, so it is still open as far as the record shows. The third involved SMS delivery delays from a subset of Twilio long codes to Telenet BidCo NV subscribers in Belgium, reaching a monitoring update at 12:01 UTC without a formal resolution filed afterward. Across the day Twilio posted 16 updates total, moving each incident through investigating, identified or monitoring, and resolved stages on its own timeline. Two components appear on Twilio's list: SMS in Europe and Verify Silent Network Auth. No user reports were filed during the window on this page. Twilio's own filings are the only record here, there is no independent confirmation beyond what the company chose to publish. The cause behind the AT&T SNA failures and the Belgium SMS delays is not on the record beyond "identified" with no further detail given.
Learning
UptimeRobot's own probes against Twilio's API, run from EU and North America regions every 60 seconds, showed 100% uptime across the last 24 hours, 7 days and 30 days, with this incident not registered against those checks. That is not a contradiction. The faults Twilio described sit in SMS and SNA delivery paths to specific carriers in specific countries, a layer that a general API health check to Twilio's own endpoint does not exercise. Your own monitoring of your integration would show the same thing: your calls to Twilio's API succeed, but messages or verifications routed through the affected carrier silently delay or fail over to a fallback method. This is the shape to watch for: green checks on your side, real delivery problems on routes you cannot see until a customer complains. Twilio's history over 90 days shows 530 incidents with a median duration of 5 hours 22 minutes, so carrier-specific delays of this kind are a routine part of running on this provider, not a one-off. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
