Some Customers May Have Incorrect Balances Reflected on Their Account
SendGrid reports incorrect balances on customer accounts. The problem affects Billing and TWILIO PLATFORM - Billing. SendGrid is investigating the problem.
State
Investigating
Started
2 h ago
2026-11-02 16:37 UTC
Ongoing for
2 h 3 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
2 h 3 min 100%
Updates
Times in UTCAs posted by SendGrid
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.
Affected components
2SendGrid in the last 90 days
Full historyIncidents in 90 days
57
Days with an incident
38
Median duration
7 h 14 min
This incident
72% shorter than the median
Other SendGrid incidents
All incidentsSendGrid·SMS Delivery Delays and Failures from Twilio Alphanumeric Sender Type to T-Mobile Austria
SendGrid reports SMS delivery delays and failures for messages from Twilio Alphanumeric Sender Type to T-Mobile subscribers in Austria. The affected components are SMS, Europe and CARRIER NETWORK - SMS, Europe. SendGrid identified the cause and is working to resolve the issue.
SendGrid·SMS Delivery Delays from a Subset of Twilio Long Codes to T-Mobile and O2 Czech Republic
SendGrid reports SMS delivery delays from a subset of Twilio Long Codes to T-Mobile and O2 Czech Republic subscribers. The incident is resolved. It lasted about 2 hours and 54 minutes.
SendGrid·Silent Network Authentication (SNA) Missing Redirects on XL Axiata in Indonesia
SendGrid reports that Silent Network Authentication (SNA) does not work on the XL Axiata network in Indonesia. Device verification during API transactions can time out on Verify Silent Network Auth. SendGrid reports the state as monitoring.
SendGrid·Voice Call Failures From a Subset of Twilio Philippines Phone Numbers to Multiple Networks in Philippines
SendGrid reports voice call failures from a subset of Twilio Philippines phone numbers. The calls do not connect to subscribers on many networks in the Philippines. The Voice, APAC and CARRIER NETWORK - Voice, APAC components are degraded. Twilio identified the cause and works to resolve the issue.
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, North America and CARRIER NETWORK, SMS Short Code, North America. SendGrid resolved the incident after about 6 hours and 33 minutes.
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.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