Live

United Kingdom Account Security Carrier Partner Maintenance - EE

MaintenanceOfficial update

Our carrier partner EE United Kingdom is conducting a planned maintenance from 17 November 2026 at 14:00 PST until 18 November 2026 at 01:20 PST. During the maintenance window, there could be intermittent API request failures for EE United Kingdom customers. Impacted Products: Verify Silent Network Auth, Lookup Identity Match, Lookup SIM Swap, Legacy Identity MatchAndAttributes

The latest update from Twilio.

State

Scheduled

Starts

in 15 d

2026-11-17 22:00 UTC

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Twilio

Scheduled2026-11-02 11:00 UTC

Our carrier partner EE United Kingdom is conducting a planned maintenance from 17 November 2026 at 14:00 PST until 18 November 2026 at 01:20 PST. During the maintenance window, there could be intermittent API request failures for EE United Kingdom customers. Impacted Products: Verify Silent Network Auth, Lookup Identity Match, Lookup SIM Swap, Legacy Identity MatchAndAttributes

Affected components

6
Verify Silent Network AuthLookup Identity MatchLookup SIM SwapCARRIER NETWORK - Verify Silent Network AuthCARRIER NETWORK - Lookup Identity MatchCARRIER NETWORK - Lookup SIM Swap

Twilio in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

55

Days with an incident

38

Median duration

7 h 14 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 14 min
90 days agoToday

Other Twilio incidents

All incidents

Twilio·SMS Delivery Delays from a Subset of Twilio Long Codes to T-Mobile and O2 Czech Republic

Twilio SMS delivery delays affected a subset of Twilio Long Codes to T-Mobile and O2 network subscribers in the Czech Republic. Twilio reports the incident resolved. It lasted about 2 hours and 54 minutes.

Resolvedresolved 7 min ago

Twilio·Silent Network Authentication (SNA) Missing Redirects in Indonesia

Twilio reports device verification timeouts during API transactions for Silent Network Authentication in Indonesia. The affected components are Verify Silent Network Auth and CARRIER NETWORK - Verify Silent Network Auth. Twilio has identified the issue and continues to investigate. API transactions may fail over to secondary methods such as SMS OTP.

Degradedupdated 2 h ago

Twilio·Voice Call Failures from a Subset of Twilio Phone Numbers to Multiple Networks in Philippines

Voice calls fail from some Twilio Philippines phone numbers to subscribers on multiple networks in the Philippines. The Voice and carrier network components in APAC are affected. Twilio has identified the cause and is working to resolve the issue.

Degradedupdated 4 h ago

Twilio·SMS Delivery Delays from a Subset of Twilio Short Codes to Google Voice United States

Twilio SMS delivery from a subset of Twilio Short Codes to Google Voice subscribers in the United States had delays. The SMS Short Code components in North America were affected. Twilio reports that the incident is resolved and the service operates normally. The incident lasted about 6 hours and 32 minutes.

Resolvedresolved 5 h ago

Twilio·SMS Delivery Failures from Twilio to KDDI Japan

SMS delivery failures from Twilio to KDDI network subscribers in Japan affected SMS in the APAC region. Twilio reports that the incident is resolved. The outage lasted about 4 hours and 8 minutes.

Resolvedresolved 12 h ago

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