Gateway API (Lookup API) Failure Increase in Canada
Twilio reports failures for Lookup API transactions in Canada. The affected components are Lookup SIM Swap and CARRIER NETWORK - Lookup SIM Swap. Twilio is investigating the issue.
State
Investigating
Started
Ongoing for
1 h 1 min
Worst impact
Degraded
Timeline
1 updateInvestigating
1 h 1 min 100%
Updates
Times in UTCAs posted by Twilio
Twilio customers may be experiencing failure responses for Lookup API transactions in Canada. 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
175
Days with an incident
58
Median duration
5 h 34 min
This incident
82% shorter than the median
Other Twilio incidents
All incidentsTwilio·Twilio Help Center Chat Creation and Retrieval Failures
Twilio Help Center chat creation and retrieval failed, which affected the Customer Support Center and the Twilio Platform Customer Support Center. Twilio reports that the incident is resolved and lasted 93 minutes. Twilio said customers who could not continue an existing chat could start a new chat.
Twilio·SMS Delivery Receipt Delays from a Subset of Twilio Phone Numbers to CTBC Brazil
SMS delivery receipts from a subset of Twilio phone numbers to CTBC network subscribers in Brazil were delayed. Twilio identified the cause and later saw a recovery. The incident is resolved and lasted about 5 hours and 14 minutes.
Twilio·Subset of API Requests Blocked with 403 Response
A subset of Twilio REST API requests are blocked with a 403 response. Twilio reports that the incident is resolved and that service is fully restored. It lasted 50 minutes, from 17:06 UTC to 17:56 UTC on 20 November 2026.
Twilio·SMS Delivery Delays from Twilio to Proximus Belgium
SMS delivery delays affected Twilio messages to Proximus network subscribers in Belgium. Twilio reports that the incident is resolved and SMS delivery is operating normally. The incident lasted about 7 hours.
Twilio·On Call Engineers are Investigating
Twilio reported a problem with User Account Roles on the Twilio Platform in the Other component. Twilio investigated the issue and then reported it resolved. The incident lasted about 18 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