Twilio outage on October 19, 2026: RCS Delivery Receipt Delays for AT&T
Twilio reported an incident affecting Twilio for 2 hours 27 minutes on 19 October 2026, from 17:21 to 19:48 UTC.
Resolved
Official incident reported by Twilio
- Started
- 17:21
- 19 Oct 2026 UTC
- Resolved
- 19:48
- 19 Oct 2026 UTC
- Duration
- 2h 27m
- 2 hours 27 minutes
- Impact
- Minor
- as rated by Twilio
- Updates
- 4
- posted by Twilio
Timeline
All times UTC.
Official incident from Twilio
RCS Delivery Receipt Delays for AT&T
-
Official
Investigating
We are investigating an issue with RCS. Users may experience delays in delivery receipts and delays with inbound messages. We will provide another update in 1 hour or as soon as more information becomes available.
-
Official
Identified
We have identified an issue with RCS. Users may experience delays in delivery receipts and delays with inbound messages. We will provide another update in 1 hour or as soon as more information becomes available.
-
Official
Monitoring
Our engineers have mitigated the issue and are monitoring system performance. Delivery receipts and inbound messages are returning to normal for RCS traffic with AT&T. We will provide another update in 2 hours or as soon as more information becomes available.
-
Official
Resolved
We have monitored and resolved the issue with RCS. All services are now operating normally at this time.
"Official" rows are quoted from Twilio's public status page, status.twilio.com. Very long posts are shortened.
What our checkpoints saw
HostTracker's checkpoints, which test www.twilio.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live Twilio status shows what our checks see right now.
Does your product depend on Twilio?
An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.
You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.
Independent measurement by HostTracker. Not affiliated with Twilio. Official updates are quoted from Twilio's public status page and remain Twilio's own words.