Live

SMS Delivery Delays and Failures from Twilio to Brisanet Brazil

0

Twilio SMS messages to Brisanet network subscribers in Brazil have delivery delays and delivery failures. The affected components are SMS in Latin America and the carrier network for SMS in Latin America. Twilio has identified the cause and is working to resolve the issue.

State

Identified

Started

Ongoing for

22 min

Worst impact

Degraded

Timeline

4 updates
20:3220:3720:4320:4820:54
DegradedNoticeUpdate postedTimes in UTC

Investigating

7 min 32%

Resolved

3 min 14%

Identified

12 min 55%

Updates

Times in UTC

As posted by Twilio

Identified

Twilio customers may be experiencing SMS delivery delays and delivery failures from Twilio 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.

Investigating

Twilio customers may be experiencing SMS delivery delays and delivery failures from Twilio to Brisanet network subscribers in Brazil. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.

Resolved
Investigating

Twilio customers may be experiencing SMS delivery delays and delivery failures from Twilio to Brisanet network subscribers in Brazil. Our team is actively investigating this 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

124

Days with an incident

48

Median duration

6 h 53 min

This incident

95% 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 53 min
90 days agoToday

Other Twilio incidents

All incidents

Twilio·Email Delivery Delays to Microsoft Inbox Providers

Twilio reports delays for Email delivery to some Microsoft-hosted inboxes. Other inbox providers are not affected. Twilio identified a third-party provider dependency. Messages to Microsoft inboxes can stay queued longer than usual, but no mail loss occurs at this time.

Degraded

Twilio·SMS Delivery Failures from Twilio to Claro Colombia

Twilio SMS delivery to Claro network subscribers in Colombia is degraded. This affects SMS, Latin America and CARRIER NETWORK - SMS, Latin America. Twilio reports that the state is investigating.

Degraded

Twilio·Voice Call Silent and One-Way Audio from Colombia to a Subset of Twilio Phone Numbers

Twilio reports silent and one-way audio on voice calls from Colombia to a subset of Twilio Phone Numbers. The affected components are Voice, Latin America and the carrier network for Voice, Latin America. Twilio has identified the cause and is working to resolve the issue.

Degraded

Twilio·SMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Networks in France

SMS delivery delays affect a subset of Twilio Long Codes that send to multiple networks in France. The affected components are SMS, Europe and CARRIER NETWORK - SMS, Europe. Twilio reports a recovery and monitors service stability.

Degraded

Twilio·SMS Delivery Delays from Twilio to Virgin Mobile Colombia

SMS delivery delays affected Twilio messages to Virgin Mobile subscribers in Colombia. The issue affected SMS services in Latin America and the related carrier network. Twilio reports that the incident is resolved. The outage lasted about 5 hours and 14 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