Minor impactResolvedCommunication

Twilio incident: RCS Inbound Events Delayed

Twilio reported this minor-impact incident on its official status page on Oct 22, 2026, 04:30 UTC. It was resolved after 46 min.

Right now Twilio is operational. Live Twilio status →

🔔 Get alerted when Twilio has issuesFree · email alerts · no credit card
Oct 22, 2026, 04:30 UTC
started
Oct 22, 2026, 05:16 UTC
resolved
46 min
duration
Minor
impact

Affected components

  • RCS Messaging
  1. resolvedOct 22, 2026, 05:16 UTC

    RCS inbound events has been resolved and RCS Messaging, is operating normally at this time.

  2. identifiedOct 22, 2026, 04:34 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.

  3. investigatingOct 22, 2026, 04:30 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Twilio's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Twilio have incidents?

Twilio reported 494 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 5h 54m. See Twilio's uptime and incident history