Skip to main content
Menu
SendGrid

Incident

Twilio Email Send API Message Delivery Delays to Microsoft Inboxes

Degraded Lasted 1d 10h · started · SendGrid's page

DWN-46c1aeb98d

Level
confirmed
Worst impact
Degraded
Components
API v3, SMTP, API v2
Down Index
40of 100

Summary

The provider says email delivery to Microsoft-hosted inboxes was delayed by a third-party provider dependency, with no mail loss. Delivery has returned to normal and deferred messages have been processed, and monitoring continues pending Microsoft's confirmation of full recovery.

Written by anthropic/claude-haiku-5.5 from SendGrid's own updates.

What to do

  • Check whether you use SendGrid API v3, SMTP, API v2. Check your stack

    Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 1d 10h it lasted.

    Anything that failed between 2026-11-12 19:42 UTC and 2026-11-14 05:51 UTC may need a replay.
  • Subscribe to SendGrid's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=sendgrid works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from SendGrid 16

  1. investigating

    We have identified an issue with Email. Users may experience delays in message delivery to some inboxes hosted by Microsoft This does not impact mail send targeted to other inbox provider other than Microsoft. We will provide another update in 1 hour or as soon as more information becomes available.

    provider

  2. identified

    We have identified the issue of delayed email delivery to Microsoft inbox providers for Email. Due to a third-party provider dependency, messages to these inboxes may remain queued longer than usual, but there is no mail loss at this time. We will provide another update in 1 hour or as soon as more information becomes available.

    provider

  3. identified

    We have identified the issue of delayed email delivery to Microsoft inbox providers for Email Inbox Providers. Due to a third-party provider dependency, messages sent to these inboxes are being deferred and queued for later delivery. There is no mail loss at this time. We will provide another update in 2 hours or as soon as more information becomes available.

    provider

  4. identified

    We have identified the issue of delays in email delivery to Microsoft-hosted inboxes. Due to a third-party provider dependency, messages to these inboxes may continue to be deferred before delivery. Mail is continuing to queue and is not being dropped at this time. We will provide another update in 4 hours or as soon as more information becomes available.

    provider

  5. identified

    We have identified the issue of delays in email delivery to Microsoft inbox providers. Due to a third-party provider dependency, messages may continue to be deferred before reaching recipient inboxes, though no mail is being dropped at this time. We will provide another update by 10:00PM PST or as soon as more information becomes available.

    provider

  6. identified

    We have identified the issue of delayed email delivery to Microsoft inboxes. Due to a third-party provider dependency, messages may continue to be deferred before reaching recipient inboxes, though mail send is not impacted and queued messages will continue to retry. We will provide another update by 7:00AM PST or as soon as more information becomes available.

    provider

  7. 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 delivery rates are showing improvement and recovery is still in progress. No mail send impact is expected, and delayed messages will continue to be retried. We will provide another update at 7:00 AM or as soon as more information becomes available.

    provider

  8. identified

    We have identified the issue of delayed email delivery to Microsoft inboxes. Due to a third-party provider dependency, some messages may continue to be deferred before reaching recipient inboxes, though we are seeing early signs of stabilization and improvement. Delayed messages continue to be retried and preserved for delivery as service recovery progresses. We will provide another update in 1 hour, 18 minutes or as soon as more information becomes available.

    provider

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

    provider

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

    provider

  11. identified

    We have identified the issue of delayed email delivery to Microsoft inboxes for Email. Due to a third-party provider dependency, delivery rates continue to improve, though some messages may still be deferred before reaching recipient inboxes. Deferred messages continue to be retried and preserved for delivery as recovery progresses, and no action is required from customers at this time. We will provide another update in an hour or as soon as more information becomes available.

    provider

  12. identified

    We have identified the issue of delayed email delivery to Microsoft inboxes for the Twilio Email Send API. Due to a third-party provider dependency, delivery rates continue to improve, but some messages may still be deferred before reaching recipient inboxes. Delayed messages continue to be retried and preserved for delivery as service recovery progresses. This does not impact mail send. We will provide another update in 2 hours or as soon as more information becomes available.

    provider

  13. monitoring

    Mail Delivery to Microsoft Inboxes has recovered at its pre-incident level and we continue to monitor and will provide another update in 2 hours or as soon as more information becomes available.

    provider

  14. monitoring

    Email delivery to Microsoft inboxes has returned to normal levels, and previously deferred messages have been processed. We will continue to monitor until we get a confirmation from MSFT that the outage is fully recovered and we will provide another update in 2 hours or as soon as more information becomes available.

    provider

  15. monitoring

    Email delivery to Microsoft inboxes has returned to normal levels and previously deferred messages have been processed. We will continue to monitor until we get a confirmation from MSFT that the outage is fully recovered and we will provide another update as soon as more information becomes available.

    provider

  16. resolved

    We have monitored and resolved the issue with the Twilio Email Send API. All services are now operating normally at this time.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-46c1aeb98d

Is SendGrid still down?

No, this incident was resolved 2026-11-14 05:51 UTC. For SendGrid's live state, see https://down.guide/providers/sendgrid.

How long did it last?

1d 10h, from 2026-11-12 19:42 UTC to 2026-11-14 05:51 UTC, by the times SendGrid posted.

What was affected?

SendGrid named API v3, SMTP, API v2.

What caused it?

SendGrid hasn't published a root cause. If it does, it shows here.

Where does this come from?

SendGrid's official status page, https://status.twilio.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.