RCS Delivery Receipt Delays for AT&T

What to do

• Check whether you use Twilio RCS Messaging. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 2h 27m it lasted.

  Anything that failed between 2026-10-19 17:21 UTC and 2026-10-19 19:48 UTC may need a replay.

• Subscribe to Twilio's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=twilio works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Twilio 4

1. investigatingOct 19, 2026, 5:21 PM UTC

   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.

   provider

2. identifiedOct 19, 2026, 5:53 PM UTC

   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.

   provider

3. monitoringOct 19, 2026, 6:43 PM UTC

   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.

   provider

4. resolvedOct 19, 2026, 7:48 PM UTC

   We have monitored and resolved the issue with RCS. All services are now operating normally at this time.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.