Live

Voice Call Audio Delays

0

Twilio voice calls from network subscribers to Twilio Phone Numbers can have audio delays and high packet loss. The affected components are Voice and CARRIER NETWORK Voice in North America, Latin America, APAC, Europe, and the Middle East and Africa. Twilio reports a recovery and monitors service stability.

State

Monitoring

Started

2 h ago

2026-11-03 02:17 UTC

Ongoing for

1 h 37 min

Worst impact

Degraded

Timeline

2 updates
02:1702:4203:0603:3003:55
DegradedUpdate postedTimes in UTC

Investigating

45 min 47%

Monitoring

52 min 53%

Updates

Times in UTC

As posted by Twilio

Monitoring2026-11-03 03:03 UTC

We have observed a recovery in voice calls from network subscribers to Twilio Phone Numbers and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.

Investigating2026-11-03 02:18 UTC

Twilio customers may be experiencing voice call audio delays and high packet loss. 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

10
Voice, North AmericaVoice, Latin AmericaVoice, APACVoice, EuropeVoice, Middle East & AfricaCARRIER NETWORK - Voice, North AmericaCARRIER NETWORK - Voice, Latin AmericaCARRIER NETWORK - Voice, APAC

Twilio in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

65

Days with an incident

39

Median duration

6 h 32 min

This incident

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

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