Voice Call Failures from a Subset of Twilio Phone Numbers to Philippines
SendGrid reports voice call failures from a subset of Twilio Philippines phone numbers to network subscribers in the Philippines. The failures affect Voice, APAC and the carrier network for Voice, APAC. SendGrid has identified the cause and is working to resolve the issue.
State
Identified
Started
2 h ago
2026-11-02 05:41 UTC
Ongoing for
1 h 59 min
Worst impact
Degraded
Timeline
5 updatesInvestigating
4 min 3%
Identified
1 h 55 min 97%
Updates
Times in UTCAs posted by SendGrid
Twilio customers may be experiencing voice call failures from a subset of Twilio Phone Numbers to network subscribers in the Philippines. 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 voice call failures from a subset of Twilio Philippines Phone Numbers to network subscribers on multiple networks in the Philippines. 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 voice call failures from a subset of Twilio Phone Numbers to network subscribers in the Philippines. 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 voice call failures from a subset of Twilio Philippines Phone Numbers to network subscribers on multiple networks in the Philippines. 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 voice call failures from a subset of Twilio Philippines Phone Numbers to network subscribers on multiple networks in the Philippines. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.
Affected components
2SendGrid in the last 90 days
Full historyIncidents in 90 days
54
Days with an incident
38
Median duration
8 h 25 min
This incident
76% shorter than the median
Other SendGrid incidents
All incidentsSendGrid·Silent Network Authentication (SNA) Missing Redirects in Indonesia
SendGrid reports that Silent Network Authentication (SNA) fails to return redirects in Indonesia. This affects Verify Silent Network Auth and the CARRIER NETWORK Verify Silent Network Auth component. SendGrid identified the problem and states that API transactions can temporarily use SMS OTP instead.
SendGrid·SMS Delivery Delays from a Subset of Twilio Short Codes to Google Voice United States
SendGrid reports SMS delivery delays from a subset of short codes to Google Voice subscribers in the United States. The affected components are SMS Short Code and CARRIER NETWORK - SMS Short Code in North America. SendGrid resolved the incident after 6 hours and 32 minutes.
SendGrid·SMS Delivery Failures from Twilio to KDDI Japan
SendGrid reports SMS delivery failures from Twilio to KDDI network subscribers in Japan. The affected components are SMS, APAC and CARRIER NETWORK - SMS, APAC. Twilio identified the cause and monitored a recovery. The incident is resolved and lasted 4 hours and 8 minutes.
SendGrid·Silent Network Authentication (SNA) Missing Redirects and Gateway API (Lookup API) High Latency on KPN in Netherlands
The incident has been resolved and API transactions for Silent Network Authentication (SNA) on KPN in Netherlands and Lookup API transactions involving KPN in Netherlands are operating normally.
SendGrid·Silent Network Authentication (SNA) Missing Redirects on Smart in Philippines
The incident has been resolved and API transactions for Silent Network Authentication (SNA) on Smart in Philippines are operating normally.
Follow SendGrid
Your coding agent knows when SendGrid is down, and tells you when a failure is theirs, not yours. You can also get SendGrid 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 "sendgrid" and tell me if SendGrid 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=sendgrid/feed subscribe https://outages.live/feed.xml?providers=sendgridFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane