Twilio: Conversations Service Returning 5xxs
Timeline of updates
- resolved
A set of Twilio services (Twilio Conversations, Sync, Verify and Flex) were degraded for 1 minute between 05:07 and 05:08 Pacific Time. During this period of time customers may have experienced and elevated number of 5xx errors and latency on the API endpoints. Additionally, SDKs might have had issues connecting to Twilio websocket infrastructure. It is possible that due to degradation of the Twilio Conversations services, Default Conversation Service can be incorrect for some customers. If this is the case, please update the Default Service in Twilio Console under Conversations and report the issue to Twilio Support for Tracking Purposes. The issue has now been resolved.
From Twilio’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.twilio.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Twilio, started 2023-06-03 13:22 UTC, resolved after 42 min, 1 update(s).
- Title
- Conversations Service Returning 5xxs
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/5bsrby45tv0n
Twilio profileRecent Twilio incidentsAll outages on June 3, 2023Twilio in June 2023MarkdownJSON