Live

Twilio Help Center Chat Creation and Retrieval Failures

Twilio Help Center chat creation and retrieval failed, which affected the Customer Support Center and the Twilio Platform Customer Support Center. Twilio reports that the incident is resolved and lasted 93 minutes. Twilio said customers who could not continue an existing chat could start a new chat.

State

Resolved

Started

Lasted

1 h 33 min

Worst impact

Degraded

Timeline

4 updates
22:2322:4723:1023:3323:56
DegradedUpdate postedTimes in UTC

Investigating

21 min 23%

Identified

42 min 45%

Monitoring

29 min 31%

Updates

Times in UTC

As posted by Twilio

Resolved

We have monitored and resolved the issue with Twilio Help Center. All services are now operating normally at this time.

Monitoring

Our engineers have mitigated the issue and are monitoring system performance. Chat creation and retrieval in the Twilio Help Center have returned to normal, and customers who still cannot continue an existing chat may start a new chat. We will provide another update in 2 hours or as soon as more information becomes available.

Identified

We have identified the issue of chat creation and chat retrieval problems for Twilio Help Center Chat. We are working toward a fix. A portion of chats may continue to be affected. We will provide another update in 1 hour or as soon as more information becomes available.

Investigating

We are experiencing chat failures from our Help Center Assistant. Our engineers are working to resolve the issue. We expect to provide another update in 1 hour or as soon as more information becomes available.

Affected components

2
Customer Support CenterTWILIO PLATFORM - Customer Support Center

Twilio in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

175

Days with an incident

58

Median duration

5 h 34 min

This incident

72% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

33 days
median 5 h 34 min
90 days agoToday

Other Twilio incidents

All incidents

Follow Twilio

Your coding agent knows when Twilio is down, and tells you when a failure is theirs, not yours. You can also get Twilio incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "twilio" and tell me if Twilio has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=twilio
Slack
/feed subscribe https://outages.live/feed.xml?providers=twilio

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane