Voice Call Failures From a Subset of Twilio Phone Numbers to Argentina
The incident has been resolved and voice calls from a subset of Twilio Phone Numbers to network subscribers in Argentina are operating normally.
The latest update from SendGrid.
State
Resolved
Started
5 d ago
2026-10-27 22:28 UTC
Lasted
19 h 41 min
until 2026-10-28 18:09 UTC
Worst impact
Degraded
Timeline
10 updatesInvestigating
8 h 29 min 43%
Identified
10 h 13 min 52%
Monitoring
59 min 5%
Updates
Times in UTCAs posted by SendGrid
The incident has been resolved and voice calls from a subset of Twilio Phone Numbers to network subscribers in Argentina are operating normally.
We have observed a recovery in voice calls from a subset of Twilio Phone Numbers to network subscribers in Argentina and are monitoring service stability. 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 Phone Numbers to network subscribers in Argentina. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 8 hours 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 Argentina. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 4 hours 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 Argentina. 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 Phone Numbers to network subscribers in Argentina. 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 Argentina. Our team is actively investigating this issue. We will provide another update in 8 hours 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 Argentina. Our team is actively investigating this issue. We will provide another update in 4 hours 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 Argentina. Our team is actively investigating this 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 Phone Numbers to network subscribers in Argentina. 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
2Follow 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.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 "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.cc/feed.xml?providers=sendgrid/feed subscribe https://outages.cc/feed.xml?providers=sendgridFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane