Transactional Email Delays in AP
Our engineers have investigated and resolved an issue with transactional email. From 5:41AM PST to 6:15AM PST on Wednesday, 11/18/26, customers may have experienced elevated latency when sending transactional email. The issue has been resolved and all impacted services are operating normally.
The latest update from SendGrid.
State
Monitoring
Started
Ongoing for
47 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
16 min 35%
Monitoring
30 min 65%
Updates
Times in UTCAs posted by SendGrid
Our engineers have investigated and resolved an issue with transactional email. From 5:41AM PST to 6:15AM PST on Wednesday, 11/18/26, customers may have experienced elevated latency when sending transactional email. The issue has been resolved and all impacted services are operating normally.
We are investigating an issue with mail send. Users may experience elevated latency when sending transactional emails in AP. 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
77
Days with an incident
48
Median duration
9 h 1 min
This incident
91% shorter than the median
Other SendGrid incidents
All incidentsSendGrid·Degraded performance
SendGrid reported degraded performance for the Mailsend Comms API component. SendGrid reports that the incident is resolved. The incident lasted from 14 November 2026 to 18 November 2026.
SendGrid·Degraded performance
SendGrid reported degraded performance on Mailsend: Comms API, API v3, SMTP, and API v2. SendGrid reports that this incident is resolved. The incident lasted 66 minutes.
SendGrid·Degraded performance
SendGrid reported degraded performance on Mailsend: Comms API, API v3, SMTP, and API v2. SendGrid reports that the incident is resolved. The incident lasted 3 minutes.
SendGrid·Email Delivery Delays to Microsoft Inboxes
SendGrid reported delayed email delivery to Microsoft inboxes. The problem affected API v3, SMTP, and API v2. SendGrid resolved the issue on 14 November 2026. The incident lasted about 34 hours.
SendGrid·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.
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