Duration: 14 hours and 56 minutes

Affected Components:

Oct 10, 00:40:51 GMT+0
Resolved - All queued messages have been processed..

Oct 10, 00:32:57 GMT+0
Monitoring - Messages are flowing again. We will continue to monitor..

Oct 10, 00:31:29 GMT+0
Identified - We found the issue. We believe it's an issue with our cloud provider. Fix is being rolled out..

Oct 10, 00:25:55 GMT+0
Investigating - Messages are being queued resulting in delayed sends..

Duration: 1 day, 12 hours and 48 minutes

Affected Components:

Oct 9, 23:52:01 GMT+0
Resolved - This incident has been resolved..

Oct 9, 23:42:48 GMT+0
Monitoring - All queued messages have been processed. We will continue to monitor..

Oct 9, 23:39:24 GMT+0
Monitoring - The fix has been deployed and the queued messages are beginning to be processed again.

Oct 9, 23:26:58 GMT+0
Identified - Issue has been identified and we are working to roll out a fix. All messages that have been queued up will be sent..

Oct 9, 23:15:13 GMT+0
Investigating - We are currently investigating an issue with delayed messages..

Affected Components:

Sep 21, 15:09:15 GMT+0
Resolved - Starting on 09/21/26 14:27 UTC Twilio customers experienced API errors affecting multiple services. Affected Components: Phone Numbers Account Management Authy > Verify Programmable Messaging > SMS Programmable Messaging > Messaging Services Programmable Messaging > MMS Programmable Messaging > Conversations Programmable Video > Group Rooms Serverless > Studio Serverless > Sync Flex > TaskRouter. The issue was resolved on 09/21/26 14:28 UTC.

Affected Components:

Sep 9, 17:47:18 GMT+0
Resolved - Our engineers have investigated and resolved an issue with Messaging Services. From 10:28AM PDT on Tuesday, 7/21/26 to 6:00PM PDT on Friday, 9/4/26, customers may have experienced HTTP 400 responses with Twilio error code 21620 when sending messages through Messaging Services if the media URL parameter contained a comma. The issue has been resolved and all impacted services are operating normally..

Duration: 4 days, 21 hours and 17 minutes

Affected Components:

Jun 18, 22:09:09 GMT+0
Resolved - Send pipeline has resolved and enqueued messages are now sending properly..

Jun 18, 21:53:47 GMT+0
Monitoring - Messages are being processed while our pipeline continues to process enqueued messages..

Jun 18, 21:31:00 GMT+0
Identified - The team has identified that the most recent deployment was not the cause of the regression. The team is still working on identifying the root cause. Messages will not be dropped, and they will be processed once the fix is out..

Jun 18, 20:35:18 GMT+0
Identified - The rollback deploy will land in about 30 minutes..

Jun 18, 20:11:52 GMT+0
Identified - The team has identified a regression causing send requests to be stuck in a queued state. We have initiated a rollback to quickly resolve the issue. More updates to follow.