Gateway API (Lookup API) Failure Increase in United States
Twilio reports failure responses for Lookup API transactions in the United States. The affected components are Lookup SIM Swap and CARRIER NETWORK - Lookup SIM Swap. Twilio has identified the cause and is working to resolve the issue.
State
Identified
Started
Ongoing for
1 h 33 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
12 min 13%
Identified
1 h 22 min 87%
Updates
Times in UTCAs posted by Twilio
Twilio customers may be experiencing failure responses for Lookup API transactions in the United States. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available.
Twilio customers may be experiencing failure responses for Lookup API transactions in the United States. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.
Twilio customers may be experiencing failure responses for Lookup API transactions in the United States. Our team is actively investigating the issue. 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
139
Days with an incident
51
Median duration
6 h 40 min
This incident
77% shorter than the median
Other Twilio incidents
All incidentsTwilio·New Twilio Accounts Experiencing Email Product Provisioning Delays
New Twilio accounts have delays with email product provisioning on the Twilio Platform in the Other component. Twilio reports signs of recovery and is monitoring the issue.
Twilio·SMS Delivery Delays from Twilio to Altan Redes Mexico
Twilio SMS delivery to Altan Redes network subscribers in Mexico had delays. The SMS and carrier network components in Latin America were affected. Twilio resolved the incident. The disruption lasted about 11 hours and 23 minutes.
Twilio·SMS Delivery Delays from Twilio to Orange Mali
SMS delivery delays affected Twilio customers who send messages to Orange network subscribers in Mali. Twilio reported the incident as resolved and said SMS delivery operates normally again. The incident lasted about 4 hours and 23 minutes.
Twilio·SMS Delivery Delays from Twilio to MTN Nigeria
Twilio SMS delivery delays affected MTN network subscribers in Nigeria and the SMS Middle East & Africa components. Twilio reports that the incident is resolved. The outage lasted about 17 hours.
Twilio·SMS Delivery Delays from a Subset of Twilio Phone Numbers to Telenor Pakistan
SMS delivery delays affected a subset of Twilio phone numbers that send to Telenor network subscribers in Pakistan. The SMS APAC and carrier network SMS APAC components were degraded. Twilio reports that the incident is resolved, and the outage lasted 9 hours and 5 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