Live

United Kingdom Account Security Carrier Partner Maintenance - Three

MaintenanceOfficial update

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

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 Three United Kingdom is conducting a planned maintenance from 18 November 2026 at 21:30 PST until 18 November 2026 at 23:00 PST. During the maintenance window, there could be intermittent API request failures for Three United Kingdom customers. Impacted Products: Verify Silent Network Auth, Lookup SIM Swap, Lookup Identity Match, Legacy Identity MatchAndAttributes

Affected components

8
Verify Silent Network AuthLookup Identity MatchLookup SIM SwapLegacy Identity MatchAndAttributesCARRIER NETWORK - Verify Silent Network AuthCARRIER 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

109

Days with an incident

47

Median duration

7 h 17 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 17 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.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