Live

Voice Call Failures from a Subset of Twilio phone numbers in Brasil

0

Voice calls fail from a subset of Twilio phone numbers in Brasil, which affects SIP Interface US1 and Programmable Voice US1. Twilio reports that the incident is resolved and that it lasted about 47 minutes.

State

Resolved

Started

Lasted

47 min

Worst impact

Degraded

Timeline

4 updates
11:4411:5612:0812:1912:31
DegradedUpdate postedTimes in UTC

Investigating

34 min 72%

Monitoring

13 min 28%

Updates

Times in UTC

As posted by Twilio

Resolved

We have monitored and resolved the issue with voice call failures from a subset of Twilio Phone Numbers in Brasil. All services are now operating normally at this time

Monitoring

Our engineers have mitigated the issue and are monitoring system performance.

Investigating

Twilio customers may be experiencing voice call failures from a subset of Twilio Phone Numbers in Brasil. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available

Investigating

Twilio customers may be experiencing voice call failures. 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
SIP Interface US1PROGRAMMABLE VOICE US1 - SIP Interface US1

Twilio in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

163

Days with an incident

54

Median duration

5 h 34 min

This incident

86% 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

Twilio·SMS Delivery Delays and Failures from a Subset of Twilio Short Codes to Bell and Bell Aliant Canada

Twilio SMS delivery delays and failures affect a subset of Twilio Short Codes to Bell and Bell Aliant subscribers in Canada. The affected components are SMS Short Code, North America and CARRIER NETWORK - SMS Short Code, North America. Twilio reports the status as identified and is working to resolve the issue.

Degraded

Twilio·Speech Recognition Failures in US1

Twilio reported speech recognition and real-time transcription failures in US1. The affected components include Recording Transcriptions, Speech Recognition (Gather Speech), and Realtime Transcriptions in US1, and Realtime Transcriptions in PROGRAMMABLE VIDEO. Twilio reported the incident as resolved after 2 hours and 48 minutes.

Resolved

Twilio·Programmable Messaging API Errors

Twilio had errors on the Programmable Messaging API and its SMS, MMS, and RCS Messaging components. The incident is resolved. It lasted 52 minutes, from 23:52 UTC on 17 November 2026 to 00:44 UTC on 18 November 2026.

Resolved

Twilio·Voice Call Signing Issues

Twilio Voice call signing for STIR/SHAKEN did not work for PSTN US1 and PROGRAMMABLE VOICE US1 - PSTN US1. Twilio reports that the incident is resolved and that the affected services operate normally.

Resolved

Twilio·SMS Delivery Delays and Failures from a Subset of Twilio Short Codes to AT&T Mexico

Twilio SMS delivery delays and failures affected a subset of Twilio Short Codes to AT&T network subscribers in Mexico. The incident is resolved. It lasted about 3 hours.

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