Twilio: RCS Inbound Events Delayed
Affected components: PROGRAMMABLE MESSAGING - RCS MessagingRCS Messaging
Timeline of updates
- investigating
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.
- identified
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.
- resolved
RCS inbound events has been resolved and RCS Messaging, is operating normally at this time.
Changes Rewindex caught on this incident
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
6476e7c5730bc79a…Version 2 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
31734e2cd6937153…Version 3 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
d801c16d63e82cab…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Twilio, started 2026-10-22 04:30 UTC, resolved after 46 min, 3 update(s); edited after publishing.
- Title
- RCS Inbound Events Delayed
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/5w712p03904b
Twilio profileRecent Twilio incidentsAll outages on October 22, 2026Twilio in October 2026MarkdownJSON