Transactional Email Delays in AP
Our engineers have investigated and resolved an issue with transactional email. From 5:41AM PST to 6:15AM PST on Wednesday, 11/18/26, customers may have experienced elevated latency when sending transactional email. The issue has been resolved and all impacted services are operating normally.
The latest update from Twilio.
State
Monitoring
Started
Ongoing for
47 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
16 min 35%
Monitoring
30 min 65%
Updates
Times in UTCAs posted by Twilio
Our engineers have investigated and resolved an issue with transactional email. From 5:41AM PST to 6:15AM PST on Wednesday, 11/18/26, customers may have experienced elevated latency when sending transactional email. The issue has been resolved and all impacted services are operating normally.
We are investigating an issue with mail send. Users may experience elevated latency when sending transactional emails in AP. We will provide another update in 1 hour or as soon as more information becomes available.
Affected components
2Twilio in the last 90 days
Full historyIncidents in 90 days
164
Days with an incident
54
Median duration
5 h 34 min
This incident
86% shorter than the median
Other Twilio incidents
All incidentsTwilio·Voice Call Failures from a Subset of Twilio phone numbers in Brasil
Voice calls fail from a subset of Twilio phone numbers in Brasil, which affects SIP Interface US1 and Programmable Voice US1. Twilio reports that the incident is resolved and that it lasted about 47 minutes.
Twilio·SMS Delivery Delays and Failures from a Subset of Twilio Short Codes to Bell and Bell Aliant Canada
Twilio SMS delivery delays and failures affect a subset of Twilio Short Codes to Bell and Bell Aliant subscribers in Canada. The affected components are SMS Short Code, North America and CARRIER NETWORK - SMS Short Code, North America. Twilio reports the status as identified and is working to resolve the issue.
Twilio·Speech Recognition Failures in US1
Twilio reported speech recognition and real-time transcription failures in US1. The affected components include Recording Transcriptions, Speech Recognition (Gather Speech), and Realtime Transcriptions in US1, and Realtime Transcriptions in PROGRAMMABLE VIDEO. Twilio reported the incident as resolved after 2 hours and 48 minutes.
Twilio·Programmable Messaging API Errors
Twilio had errors on the Programmable Messaging API and its SMS, MMS, and RCS Messaging components. The incident is resolved. It lasted 52 minutes, from 23:52 UTC on 17 November 2026 to 00:44 UTC on 18 November 2026.
Twilio·Voice Call Signing Issues
Twilio Voice call signing for STIR/SHAKEN did not work for PSTN US1 and PROGRAMMABLE VOICE US1 - PSTN US1. Twilio reports that the incident is resolved and that the affected services operate normally.
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