Live

Transactional Email Delays in AP

0

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 updates
14:0514:1614:2814:4014:51
DegradedUpdate postedTimes in UTC

Investigating

16 min 35%

Monitoring

30 min 65%

Updates

Times in UTC

As posted by SendGrid

Monitoring

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.

Investigating

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

2
API v3SendGrid Mail Sending - API v3

SendGrid in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

77

Days with an incident

48

Median duration

9 h 1 min

This incident

91% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

33 days
median 9 h 1 min
90 days agoToday

Other SendGrid incidents

All incidents

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=sendgrid
Slack
/feed subscribe https://outages.live/feed.xml?providers=sendgrid

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane