Live

United Kingdom Account Security Carrier Partner Maintenance - Vodafone

Scheduled maintenance is currently in progress. We will provide updates as necessary.

The latest update from Twilio.

State

Resolved

Started

Lasted

5 h 3 min

Worst impact

Maintenance

Timeline

4 updates
23:0000:1501:3102:4704:03
MaintenanceUpdate postedTimes in UTC

Scheduled

1 min 0%

In progress

5 h 3 min 100%

Updates

Times in UTC

As posted by Twilio

Resolved
In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Scheduled

Maintenance will begin as scheduled in 60 minutes.

Scheduled

<p>Our carrier partner Vodafone United Kingdom is conducting a planned maintenance from 19 November 2026 at 15:00 PST until 19 November 2026 at 20:00 PST. During the maintenance window, there could be intermittent API request failures for Vodafone United Kingdom customers.<br><br>Impacted Products: Lookup Identity Match, Legacy Identity MatchAndAttributes, Verify Silent Network Auth<br><br>We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.</p>

Affected components

6
Verify Silent Network AuthLookup Identity MatchLegacy Identity MatchAndAttributesCARRIER NETWORK - Verify Silent Network AuthCARRIER NETWORK - Lookup Identity MatchCARRIER NETWORK - Legacy Identity MatchAndAttributes

Twilio in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

170

Days with an incident

56

Median duration

5 h 47 min

This incident

Not comparable

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·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

Twilio·SMS Delivery Failures from a Subset of Twilio Phone Numbers to Zong Pakistan

SMS delivery failures affected a subset of Twilio phone numbers to Zong network subscribers in Pakistan. The incident is resolved and lasted 8 hours and 3 minutes.

Resolved

Twilio·Text to Speech Timeouts

Twilio reports timeouts when users generate speech from text through ElevenLabs Text to Speech in the US1 region, including Speech Recognition (Gather Speech) US1. Twilio later identified the issue, monitored recovery, and marked the incident resolved. The outage lasted about 4 hours and 34 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