WhatsApp Business API Message Send Failures
Twilio reports message send failures on the WhatsApp Business API, which affects WhatsApp Messaging. Some customers get error 63007 when they send outbound messages. Twilio has mitigated the issue and now monitors system performance. Message sending is returning to normal for affected customers.
State
Monitoring
Started
Ongoing for
8 h 21 min
Worst impact
Degraded
Timeline
4 updatesInvestigating
2 h 34 min 31%
Identified
1 h 57 min 23%
Monitoring
3 h 50 min 46%
Updates
Times in UTCAs posted by Twilio
Our engineers have mitigated the issue and are monitoring system performance. Message sending through the WhatsApp Business API is returning to normal for affected customers. We will provide another update in 2 hours or as soon as more information becomes available.
We have identified the issue of message send failures for WhatsApp Business API. Due to a third-party provider dependency, some customers may continue to experience error 63007 when sending messages. We are working to restore service and will provide another update in 1 hour or as soon as more information becomes available.
We are investigating an issue with the WhatsApp Business API. Users may experience intermittent message send failures with error 63007 when sending outbound WhatsApp messages. We will provide another update in 2 hours or as soon as more information becomes available.
We are investigating an issue with the WhatsApp Business API. Users may experience errors sending messages. 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
102
Days with an incident
46
Median duration
7 h 30 min
This incident
About the median
Other Twilio incidents
All incidentsTwilio·Voice Call Failures from a Subset of Twilio Phone Numbers to Chile
Voice calls fail from some Twilio phone numbers to network subscribers in Chile. The Voice, Latin America and CARRIER NETWORK - Voice, Latin America components are affected. Twilio has identified the cause and works to resolve the issue.
Twilio·Voice Call Audio Quality Degradation, Silent and One-Way Audio between Twilio and Multiple Networks in United Kingdom
Twilio voice calls had audio quality degradation, silent audio, and one-way audio between Twilio and network subscribers on multiple networks in the United Kingdom. The affected components were Voice, Europe and CARRIER NETWORK - Voice, Europe. Twilio reports that the incident is resolved, and it lasted about 5 hours and 19 minutes.
Twilio·SMS Delivery Delays and Failures from a Subset of Twilio Alphanumeric Sender IDs and Long Codes to Multiple Networks in Italy
Twilio SMS delivery delays and failures affected a subset of Twilio Alphanumeric Sender IDs and Long Codes to multiple networks in Italy. Twilio identified the cause, then monitored service stability. The incident is resolved. It lasted about 3 hours and 14 minutes.
Twilio·SMS Delivery Delays and Failures from Twilio to Spusu United Kingdom
Twilio SMS delivery delays and failures affected messages to Spusu subscribers in the United Kingdom. Twilio reports that the incident is resolved. The outage lasted 3 hours and 26 minutes.
Twilio·SMS Delivery Receipt Delays from Twilio to Bouygues Telecom France
Twilio SMS delivery receipts to Bouygues Telecom subscribers in France were delayed. The SMS Europe and CARRIER NETWORK - SMS Europe components were degraded. Twilio reports that the incident is resolved. It lasted about 13 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.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