Malaysia SMS Carrier Maintenance - Red One
The Red One network in Malaysia is conducting a planned maintenance from 12 November 2026 at 06:00 PST until 12 November 2026 at 09:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to Red One Malaysia handsets.
The latest update from Twilio.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Twilio
The Red One network in Malaysia is conducting a planned maintenance from 12 November 2026 at 06:00 PST until 12 November 2026 at 09:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to Red One Malaysia handsets.
Affected components
2Twilio in the last 90 days
Full historyIncidents in 90 days
75
Days with an incident
41
Median duration
7 h 20 min
This incident
Not comparable
Other Twilio incidents
All incidentsTwilio·Search Delays on Enterprise Knowledge
Twilio reported slower search and content ingestion on Enterprise Knowledge, including its use with Conversation Intelligence. Twilio later stated that search latency is resolved and that Enterprise Knowledge operates normally. The incident lasted about 4 hours and 33 minutes.
Twilio·Delayed Email Validation History
Twilio reported delayed Email validation history in the SendGrid UI. The Logs and TWILIO EMAIL - Logs components were affected. Twilio resolved the incident on 4 November 2026, and it lasted 2 hours and 48 minutes.
Twilio·SMS Delivery Delays from Twilio to Claro Brazil
Twilio SMS delivery to Claro network subscribers in Brazil had delays. The problem affected SMS in Latin America and the carrier network for SMS in Latin America. Twilio reports that the incident is resolved. The incident lasted about 4 hours and 44 minutes.
Twilio·SMS Delivery Delays from Twilio to Algar Telecom Brazil
Twilio SMS delivery to Algar Telecom network subscribers in Brazil had delays. The incident affected SMS in Latin America and the carrier network for SMS in Latin America. Twilio reports that the incident is resolved and that delivery is normal. The incident lasted about 5 hours and 20 minutes.
Twilio·MMS Delivery Failures from a Subset of Twilio Long Codes to GCI United States
MMS delivery failures affected a subset of Twilio Long Codes that send to GCI network subscribers in the United States. Twilio reports that the incident is resolved. The outage 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.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