Live

Email Delivery Delays to Microsoft Inboxes

0

SendGrid reported delayed email delivery to Microsoft inboxes. The problem affected the Comms API, API v3, SMTP, and API v2. SendGrid identified the issue and later marked it resolved. The outage lasted about 19 hours and 42 minutes.

State

Resolved

Started

Lasted

19 h 42 min

Worst impact

Degraded

Timeline

4 updates
19:4200:3805:3310:2915:24
DegradedNoticeUpdate postedTimes in UTC

Identified

19 h 39 min 100%

Resolved

3 min 0%

Updates

Times in UTC

As posted by SendGrid

Resolved
Identified

We have identified the issue of delayed email delivery to Microsoft inboxes for Email. Due to a third-party provider dependency, some messages may continue to be deferred before reaching recipient inboxes, though we are seeing continued improvement as queued messages are retried automatically and delivery progresses toward normal levels. No action is required from customers at this time. We will provide another update in 2 hours or as soon as more information becomes available.

Resolved
Identified

We have identified the issue of delayed email delivery to Microsoft inboxes for Email. Due to a third-party provider dependency, some messages may continue to be deferred before reaching recipient inboxes, though we are seeing continued improvement as queued messages are retried automatically and delivery progresses toward normal levels. No action is required from customers at this time. We will provide another update in 2 hours or as soon as more information becomes available.

Affected components

10
Mailsend: Comms APIAPI v3SMTPAPI v2OtherTWILIO PLATFORM - OtherTWILIO EMAIL - Mailsend: Comms APISendGrid Mail Sending - API v3

SendGrid in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

75

Days with an incident

43

Median duration

9 h 1 min

This incident

2.2× 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