Some Customers May Have Incorrect Balances Reflected on Their Account
Some Twilio customers see incorrect balances on their accounts. The Twilio Billing component is affected. Twilio reports that the incident is under investigation and that a fix is in progress.
State
Investigating
Started
2 h ago
2026-11-02 16:37 UTC
Ongoing for
2 h 5 min
Worst impact
Degraded
Timeline
5 updatesInvestigating
2 h 5 min 100%
Updates
Times in UTCAs posted by Twilio
Our engineering team is still actively investigating the issue. We will provide another update within the next hour, or sooner if additional information becomes available.
Our engineering team is still actively investigating the issue causing incorrect balances to be reflected on customer accounts. We are working to deploy a fix as quickly as possible. We will provide another update within the next hour, or sooner if additional information becomes available.
Our engineering team is actively investigating the issue causing incorrect balances to be reflected on customer accounts. We are working to deploy a fix as quickly as possible. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.
Our engineering team is still actively investigating the issue causing incorrect balances to be reflected on customer accounts. We are working to deploy a fix as quickly as possible. We will provide another update within the next hour, or sooner if additional information becomes available.
Our engineering team is actively investigating the issue causing incorrect balances to be reflected on customer accounts. We are working to deploy a fix as quickly as possible. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.
Affected components
2Twilio in the last 90 days
Full historyIncidents in 90 days
57
Days with an incident
38
Median duration
7 h 14 min
This incident
71% shorter than the median
Other Twilio incidents
All incidentsTwilio·SMS Delivery Delays and Failures from Twilio Alphanumeric Sender Type to T-Mobile Austria
Twilio SMS delivery delays and failures affect Alphanumeric Sender IDs to T-Mobile subscribers in Austria. The affected components are SMS, Europe and CARRIER NETWORK - SMS, Europe. Twilio identified the cause and works to resolve the issue.
Twilio·SMS Delivery Delays from a Subset of Twilio Long Codes to T-Mobile and O2 Czech Republic
Twilio SMS delivery delays affected a subset of Twilio Long Codes to T-Mobile and O2 network subscribers in the Czech Republic. Twilio reports that the incident is resolved. The incident lasted 2 hours and 54 minutes.
Twilio·Silent Network Authentication (SNA) Missing Redirects on XL Axiata in Indonesia
Twilio reports degradation in Verify Silent Network Auth and CARRIER NETWORK - Verify Silent Network Auth for XL Axiata in Indonesia. Device verification timeouts can occur during API transactions, and transactions may fail over to SMS OTP. Twilio says it sees recovery and monitors service stability.
Twilio·Voice Call Failures From a Subset of Twilio Philippines Phone Numbers to Multiple Networks in Philippines
Twilio reports voice call failures from some Twilio Philippines phone numbers to subscribers on multiple networks in the Philippines. The affected components are Voice, APAC and CARRIER NETWORK - Voice, APAC. Twilio states that it identified the cause and is working to resolve the issue.
Twilio·SMS Delivery Delays from a Subset of Twilio Short Codes to Google Voice United States
Twilio SMS delivery delays affected a subset of Twilio Short Codes to Google Voice subscribers in the United States, on the SMS Short Code and Carrier Network SMS Short Code components in North America. Twilio reports that the incident is resolved and that delivery operates normally. The incident lasted about 6 hours and 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.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