Email Template Editor Issues
SendGrid Marketing Campaigns had a problem with the email template editor. HTML entities changed to spaces, links changed, and some template content did not render after save or preview. SendGrid reports the incident resolved. It lasted 106 minutes.
State
Resolved
Started
Lasted
1 h 46 min
Worst impact
Degraded
Timeline
4 updatesInvestigating
16 min 15%
Identified
30 min 28%
Monitoring
1 h 57%
Updates
Times in UTCAs posted by SendGrid
Our engineers have mitigated the issue and are monitoring system performance. Customers should now be able to save HTML email templates without unexpected changes to spacing, links, or rendered content in the editor and preview. We will provide another update in 2 hours or as soon as more information becomes available.
We have identified the issue of unexpected content changes for Build Email Templates and Create Email Campaigns. Customers may see HTML entities replaced with regular spaces, links rewritten after saving, and some template content not render as expected in preview. As a workaround, customers may avoid saving changes in the HTML code editor until the issue is resolved. We will provide another update in 1 hour or as soon as more information becomes available.
We are investigating an issue with the email template editor. Users may experience HTML entities being replaced with regular spaces, links being rewritten, and portions of template content not rendering correctly after saving or previewing code, which may affect email campaign creation. We will provide another update in 1 hour or as soon as more information becomes available.
Affected components
1SendGrid in the last 90 days
Full historyIncidents in 90 days
72
Days with an incident
41
Median duration
9 h 1 min
This incident
80% shorter than the median
Other SendGrid incidents
All incidentsSendGrid·Delayed Email Validation History
SendGrid reported delayed Email Validation history and statistics in the SendGrid UI. The Logs and TWILIO EMAIL - Logs components were degraded. SendGrid resolved the incident on 4 November 2026 after 168 minutes.
SendGrid·MMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Small Carriers in United States
SendGrid reported MMS delivery delays from a subset of Twilio Long Codes to multiple small carriers in the United States. The affected components were MMS Long Code, North America. SendGrid resolved the incident after 78 minutes.
SendGrid·MMS Delivery Delays from a Subset of Twilio Long Codes and Short Codes to AT&T United States
SendGrid MMS messages from a subset of Twilio Long Codes and Short Codes to AT&T subscribers in the United States had delivery delays. The incident is resolved. It lasted about 8 hours and 26 minutes.
SendGrid·MMS Delivery Delays and Failures from a Subset of Twilio Short Codes to T-Mobile and Verizon United States
SendGrid reported that MMS delivery delays and failures affected MMS Short Code traffic in North America for a subset of Twilio Short Codes to T-Mobile and Verizon subscribers in the United States. SendGrid identified the cause and later saw a recovery in MMS delivery. SendGrid resolved the incident on 3 November 2026, about 6 hours and 18 minutes after it started.
SendGrid·SMS Delivery Delays from a Subset of Twilio Short Codes and Long Codes to Brisanet Brazil
SendGrid reported SMS delivery delays from a subset of Twilio Short Codes and Long Codes to Brisanet network subscribers in Brazil. The affected components were SMS, Latin America and CARRIER NETWORK - SMS, Latin America. SendGrid reported the incident as resolved after 14 hours and 47 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.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