Twilio: RCS Inbound Events Delayed

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 46m it lasted.
Anything that failed between 2026-10-22 04:30 UTC and 2026-10-22 05:16 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.

investigatingOct 22, 2026, 4:30 AM UTC
We are investigating an issue with inbound RCS events. Users may experience elevated HTTP 500 and 503 status codes when receiving inbound RCS events. We will provide another update in 1 hour or as soon as more information becomes available.
provider
identifiedOct 22, 2026, 4:34 AM UTC
We have identified the issue of delays with RCS inbound events. We are working toward a fix to restore normal service. We will provide another update in 1 hour or as soon as more information becomes available.
provider
resolvedOct 22, 2026, 5:16 AM UTC
RCS inbound events has been resolved and RCS Messaging, is operating normally at this time.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

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

Is Twilio still down?

No, this incident was resolved 2026-10-22 05:16 UTC. For Twilio's live state, see https://down.guide/twilio.

How long did it last?

46m, from 2026-10-22 04:30 UTC to 2026-10-22 05:16 UTC, by the times Twilio posted.

What was affected?

Twilio named RCS Messaging.

What caused it?

Twilio hasn't published a root cause. If it does, it shows here.

Where does this come from?

Twilio's official status page, https://status.twilio.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.