Search Delays on Enterprise Knowledge
Twilio reports slow search and content ingestion on Enterprise Knowledge. This also affects Enterprise Knowledge with CONVERSATIONS. Twilio is still investigating the issue.
State
Investigating
Started
Ongoing for
1 h 36 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
1 h 36 min 100%
Updates
Times in UTCAs posted by Twilio
We are continuing to investigate the issue on elevated latency when searching and ingesting content in Enterprise Knowledge. Customers using Enterprise Knowledge, including those using it with Conversation Intelligence, may see slower than normal responses. Our engineers are working to resolve the issue. We expect to provide another update in 2 hours or as soon as more information becomes available.
We are experiencing elevated latency when searching and ingesting content in Enterprise Knowledge. Customers using Enterprise Knowledge, including those using it with Conversation Intelligence, may see slower than normal responses. Our engineers are working to resolve the issue. We expect to provide another update in 1 hour or as soon as more information becomes available.
We are experiencing elevated latency when searching on Enterprise Knowledge. Customers may see slower than normal search responses. Our engineers are working to resolve the issue. We expect to 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
75
Days with an incident
40
Median duration
7 h 52 min
This incident
80% shorter than the median
Other Twilio incidents
All incidentsTwilio·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 affect Twilio messages to Claro network subscribers in Brazil. The affected components are SMS, Latin America and CARRIER NETWORK - SMS, Latin America. Twilio reports a recovery in delivery and monitors service stability.
Twilio·SMS Delivery Delays from Twilio to Algar Telecom Brazil
Twilio reports SMS delivery delays from Twilio to Algar Telecom network subscribers in Brazil. The SMS and carrier network components in Latin America are affected. Twilio observed a recovery and monitors service stability. The incident started at 16:02 UTC on 4 November 2026 and continues.
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.
Twilio·MMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Small Networks in United States
Twilio MMS delivery receipts were delayed from a subset of Twilio Long Codes to subscribers on multiple small networks in the United States. Twilio reports that the incident is resolved. The outage lasted 8 hours and 3 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