WhatsApp Sandbox Sending Configuration Issues
We have monitored and resolved the issue with WhatsApp Sandbox sender configuration. All services are now operating normally at this time.
The latest update from SendGrid.
State
Resolved
Started
6 d ago
2026-10-26 15:00 UTC
Lasted
2 h 40 min
until 2026-10-26 17:40 UTC
Worst impact
Degraded
Timeline
3 updatesInvestigating
2 h 37 min 98%
Monitoring
3 min 2%
Updates
Times in UTCAs posted by SendGrid
We have monitored and resolved the issue with WhatsApp Sandbox sender configuration. All services are now operating normally at this time.
Our engineers have mitigated the issue and are monitoring system performance. The WhatsApp Sandbox display name has been restored and the preconfigured templates have been updated. We will provide another update in 2 hours or as soon as more information becomes available.
Users may experience an incorrect display name for sandbox messages and errors sending preconfigured templates. 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
50
Days with an incident
37
Median duration
9 h 43 min
This incident
73% shorter than the median
Other SendGrid incidents
All incidentsSendGrid·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.
SendGrid·Automated Alert: Minimal Customer Impact
We have fully investigated the issue affecting verifications to Ivory Coast, and it was determined that the impact was limited to a small set of customers, who have been contacted individually to address any concerns. All systems are operational.
SendGrid·SMS and MMS Delivery Delays from Twilio to Altice United States
The incident has been resolved and SMS and MMS delivery from Twilio to Altice network subscribers in the United States is operating normally.
SendGrid·SMS Delivery Receipt Delays from Twilio to Multiple Networks in Multiple Countries Across Africa and Asia
The incident has been resolved and SMS delivery receipts from Twilio to network subscribers on affected networks in multiple countries across Africa and Asia 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.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