Egypt SMS Carrier Maintenance - Vodafone
The Vodafone network in Egypt is conducting a planned maintenance from 11 November 2026 at 15:00 PST until 11 November 2026 at 20:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to Vodafone Egypt handsets.
The latest update from Twilio.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Twilio
The Vodafone network in Egypt is conducting a planned maintenance from 11 November 2026 at 15:00 PST until 11 November 2026 at 20:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to Vodafone Egypt handsets.
Affected components
2Twilio in the last 90 days
Full historyIncidents in 90 days
103
Days with an incident
46
Median duration
7 h 52 min
This incident
Not comparable
Other Twilio incidents
All incidentsTwilio·Gateway API (Lookup API) Failure Increase on Verizon in United States
Twilio Lookup API transactions on Verizon in the United States return failure responses. The affected components are Lookup SIM Swap, Legacy Identity MatchAndAttributes, and their carrier network versions. Twilio reports recovery and monitors service stability.
Twilio·WhatsApp Business API Message Send Failures
Twilio reports that WhatsApp Business API message sends failed. The WhatsApp Messaging component was affected. Twilio reported error 63007 for outbound messages. Twilio identified a third-party provider dependency, mitigated the issue, and monitored the fix. The incident is resolved. It lasted about 16 hours and 29 minutes.
Twilio·Voice Call Failures from a Subset of Twilio Phone Numbers to Chile
Twilio voice calls failed from a subset of Twilio Phone Numbers to network subscribers in Chile. The incident affected Voice in Latin America and the carrier network for Voice in Latin America. Twilio reports that the incident is resolved and that calls operate normally. The incident lasted about 19 hours and 20 minutes.
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.
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.
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.
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.
https://outages.live/feed.xml?providers=twilio/feed subscribe https://outages.live/feed.xml?providers=twilioFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane