Live

SMS Delivery Delays from a Subset of Twilio Short Codes and Long Codes to Brisanet Brazil

0

SMS delivery delays affect a subset of Twilio Short Codes and Long Codes to Brisanet subscribers in Brazil. The SMS Latin America and carrier network SMS Latin America components are degraded. Twilio identified the cause and continues to work on the fix.

State

Identified

Started

2 h ago

2026-11-03 04:55 UTC

Ongoing for

2 h 2 min

Worst impact

Degraded

Timeline

2 updates
04:5505:2505:5606:2606:56
DegradedUpdate postedTimes in UTC

Identified

2 h 2 min 100%

Updates

Times in UTC

As posted by Twilio

Identified2026-11-03 06:00 UTC

Twilio customers may be experiencing SMS delivery delays from a subset of Twilio Short Codes and Long Codes to Brisanet network subscribers in Brazil. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available.

Identified2026-11-03 04:57 UTC

Twilio customers may be experiencing SMS delivery delays from a subset of Twilio Short Codes and Long Codes to Brisanet network subscribers in Brazil. Our team has identified the cause, and is working to resolve the issue. 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

67

Days with an incident

39

Median duration

6 h 32 min

This incident

69% shorter than the median

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

33 days
median 6 h 32 min
90 days agoToday

Other Twilio incidents

All incidents

Twilio·MMS Delivery Receipt Delays from a Subset of Twilio Long Codes to GCI Communication United States

Twilio reports delayed MMS delivery receipts from a subset of Twilio Long Codes to GCI Communication subscribers in the United States. The MMS Long Code components in North America are affected. Twilio has identified the cause and work continues. Delivery can succeed, but receipts can arrive late.

Degradedupdated 1 h ago

Twilio·SMS Delivery Delays from Twilio to Entel Bolivia

Twilio SMS messages to Entel network subscribers in Bolivia have delivery delays. The SMS and carrier network components in Latin America are affected. Twilio reports that it identified the cause and is working to resolve the issue.

Degradedupdated 2 h ago

Twilio·SMS Delivery Delays from Twilio to Lycamobile United Kingdom

Twilio SMS delivery delays affected messages to Lycamobile subscribers in the United Kingdom. The affected components were SMS, Europe and CARRIER NETWORK - SMS, Europe. Twilio resolved the incident. The outage lasted about 2 hours and 40 minutes.

Resolvedresolved 1 h ago

Twilio·Voice Call Audio Quality Degradation from Network Subscribers to Twilio Phone Numbers

Voice calls from network subscribers to Twilio phone numbers have audio delays and high packet loss. The issue affects Voice and carrier network components in North America, Latin America, APAC, Europe, and Middle East & Africa. Twilio reports a recovery in these calls and continues to monitor service stability.

Degradedupdated 2 h ago

Twilio·RateQueue Host Down Did Not Recover

Twilio reports delays for SMS and Programmable Messaging SMS. No messages are lost. Twilio identified and mitigated the issue, and continues to investigate the root cause.

Degradedupdated 2 h ago

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.cc/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.cc/feed.xml?providers=twilio
Slack
/feed subscribe https://outages.cc/feed.xml?providers=twilio

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane