Skip to content

Incident detail

RCS Inbound Events Delayed

Resolved incidentMinor1 affected service

Timeline window

to

Get alerted the next time Twilio breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. 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.

  2. 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.

  3. Resolved

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

Keep exploring

More from Twilio

Neighboring incidents on Twilio's timeline and the rest of their record on OutageDeck.