outages.live
Live
TwilioMaintenance ·

United Kingdom Account Security Carrier Partner Maintenance - Vodafone

MaintenanceOfficial update

Our carrier partner Vodafone United Kingdom is conducting a planned maintenance from 10 November 2026 at 15:15 PST until 10 November 2026 at 19:45 PST. During the maintenance window, there could be intermittent API request failures for Vodafone United Kingdom customers. Impacted Products: Legacy Identity MatchAndAttributes, Lookup SIM Swap, Lookup Identity Match We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.

The latest update from Twilio.

State

Scheduled

Starts

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Twilio

Scheduled

Our carrier partner Vodafone United Kingdom is conducting a planned maintenance from 10 November 2026 at 15:15 PST until 10 November 2026 at 19:45 PST. During the maintenance window, there could be intermittent API request failures for Vodafone United Kingdom customers. Impacted Products: Legacy Identity MatchAndAttributes, Lookup SIM Swap, Lookup Identity Match We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.

Affected components

6
Lookup Identity MatchLookup SIM SwapLegacy Identity MatchAndAttributesCARRIER NETWORK - Lookup Identity MatchCARRIER NETWORK - Lookup SIM SwapCARRIER NETWORK - Legacy Identity MatchAndAttributes

Twilio in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

103

Days with an incident

46

Median duration

7 h 30 min

This incident

Not comparable

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

33 days
median 7 h 30 min
90 days agoToday

Other Twilio incidents

All incidents

Twilio·Gateway API (Lookup API) Failure Increase on Verizon in United States

Twilio reports failure responses for Lookup API transactions on Verizon in the United States. The affected components are Lookup SIM Swap and Legacy Identity MatchAndAttributes, on the carrier network. Twilio is investigating the problem.

Degraded

Twilio·WhatsApp Business API Message Send Failures

Twilio reports message send failures on the WhatsApp Business API, which affects WhatsApp Messaging. Some customers get error 63007 when they send outbound messages. Twilio has mitigated the issue and now monitors system performance. Message sending is returning to normal for affected customers.

Degraded

Twilio·Voice Call Failures from a Subset of Twilio Phone Numbers to Chile

Voice calls from some Twilio Phone Numbers to Chile do not connect. The affected components are Voice, Latin America and CARRIER NETWORK - Voice, Latin America. Twilio reports a recovery in these calls and monitors service stability.

Degraded

Twilio·Voice Call Audio Quality Degradation, Silent and One-Way Audio between Twilio and Multiple Networks in United Kingdom

Twilio voice calls had audio quality degradation, silent audio, and one-way audio between Twilio and network subscribers on multiple networks in the United Kingdom. The affected components were Voice, Europe and CARRIER NETWORK - Voice, Europe. Twilio reports that the incident is resolved, and it lasted about 5 hours and 19 minutes.

Resolved

Twilio·SMS Delivery Delays and Failures from a Subset of Twilio Alphanumeric Sender IDs and Long Codes to Multiple Networks in Italy

Twilio SMS delivery delays and failures affected a subset of Twilio Alphanumeric Sender IDs and Long Codes to multiple networks in Italy. Twilio identified the cause, then monitored service stability. The incident is resolved. It lasted about 3 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