Chile SMS Carrier Maintenance - Nextel
The Nextel network in Chile is conducting a planned maintenance from 05 November 2026 at 00:00 PST until 05 November 2026 at 02:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to Nextel Chile handsets. 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 UTCAs posted by Twilio
The Nextel network in Chile is conducting a planned maintenance from 05 November 2026 at 00:00 PST until 05 November 2026 at 02:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to Nextel Chile handsets. We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.
Affected components
2Twilio in the last 90 days
Full historyIncidents in 90 days
75
Days with an incident
40
Median duration
7 h 52 min
This incident
Not comparable
Other Twilio incidents
All incidentsTwilio·Search Delays on Enterprise Knowledge
Twilio reports slow search and content ingestion on Enterprise Knowledge. This also affects Enterprise Knowledge with Conversation Intelligence. Twilio is investigating the issue.
Twilio·Delayed Email Validation History
Twilio reports delayed Email Validation history in the SendGrid UI logs. Users may not see recent validation results or updated totals in the validation history. Twilio identified the issue and is working on a fix. Mail send is not affected.
Twilio·SMS Delivery Delays from Twilio to Claro Brazil
SMS delivery delays occur from Twilio to Claro network subscribers in Brazil. The delays affect SMS in Latin America and the related carrier network. Twilio identified the cause and is working to resolve the issue.
Twilio·SMS Delivery Delays from Twilio to Algar Telecom Brazil
SMS delivery delays affect messages from Twilio to Algar Telecom subscribers in Brazil. Twilio reports that it identified the cause and is working to fix the problem. The incident started 67 minutes ago.
Twilio·MMS Delivery Failures from a Subset of Twilio Long Codes to GCI United States
Twilio MMS delivery failures affected a subset of Twilio Long Codes to GCI network subscribers in the United States. The components were MMS Long Code, North America and related carrier and ZIPWHIP messaging services. Twilio reports that the incident is resolved. It lasted about 32 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.cc/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.cc/feed.xml?providers=twilio/feed subscribe https://outages.cc/feed.xml?providers=twilioFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane