Live

SMS Delivery Receipt Delays from a Subset of Twilio Phone Numbers to CTBC Brazil

0

Twilio SMS delivery receipts are delayed from a subset of Twilio phone numbers to CTBC subscribers in Brazil. The affected components are SMS, Latin America and CARRIER NETWORK - SMS, Latin America. Twilio has identified the cause and is working to resolve the issue.

State

Identified

Started

Ongoing for

55 min

Worst impact

Degraded

Timeline

1 update
19:5320:0720:2120:3420:48
DegradedUpdate postedTimes in UTC

Identified

55 min 100%

Updates

Times in UTC

As posted by Twilio

Identified

Twilio customers may be experiencing SMS delivery receipt delays from a subset of Twilio Phone Numbers to CTBC network subscribers in Brazil. Our team has identified the cause, and is working to resolve the issue. Message delivery may succeed, but delivery receipts may be delayed. We will provide another update in 1 hour or as soon as more information becomes available.

Affected components

2
SMS, Latin AmericaCARRIER NETWORK - SMS, Latin America

Twilio in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

173

Days with an incident

56

Median duration

5 h 47 min

This incident

84% 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 47 min
90 days agoToday

Other Twilio incidents

All incidents

Twilio·Subset of API Requests Blocked with 403 Response

A subset of Twilio REST API requests are blocked with a 403 response. Twilio reports that the incident is resolved and that service is fully restored. It lasted 50 minutes, from 17:06 UTC to 17:56 UTC on 20 November 2026.

Resolved

Twilio·SMS Delivery Delays from Twilio to Proximus Belgium

SMS delivery delays affected Twilio messages to Proximus network subscribers in Belgium. Twilio reports that the incident is resolved and SMS delivery is operating normally. The incident lasted about 7 hours.

Resolved

Twilio·On Call Engineers are Investigating

Twilio reported a problem with User Account Roles on the Twilio Platform in the Other component. Twilio investigated the issue and then reported it resolved. The incident lasted about 18 minutes.

Resolved

Twilio·Voice Call Failures from a Subset of Twilio Phone Numbers to Argentina

Voice calls from a subset of Twilio Phone Numbers to network subscribers in Argentina failed. The Voice, Latin America and CARRIER NETWORK - Voice, Latin America components had degraded service. Twilio reports that the incident is resolved. The incident lasted about 7 hours and 38 minutes.

Resolved

Twilio·SMS Delivery Delays from Twilio to ISP Telecom United States

SMS delivery delays affected Twilio messages to ISP Telecom network subscribers in the United States. The affected components were SMS Long Code, SMS Short Code, and SMS Toll-Free in North America, including the carrier network. Twilio reports that the incident is resolved and that SMS delivery operates normally. The incident lasted about 9 hours and 37 minutes.

Resolved

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