Skip to main content
Twilio

Widespread Microsoft 365 IP Block Causing Delivery Failures for Multiple Users

Degraded Lasted 34m · started · Twilio's page

Level
confirmed
Worst impact
Degraded
Down Index
16of 100

What to do

  • Check whether your product depends on Twilio. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 34m it lasted.

    Anything that failed between 2026-08-15 01:31 UTC and 2026-08-15 02:05 UTC may need a replay.
  • Subscribe to Twilio's feed to hear about the next one first. RSS feed

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

Updates from Twilio 4

  1. monitoring

    Beginning Aug 14 2026, ~21:45 UTC, we have observed an increase of 10-15% in blocks from Microsoft 365 impacting all Twilio Sendgrid IPs. We have confirmed with other industry contacts that they are observing similar behavior. The blocks are being observed at many domains hosted by Microsoft 365 and are not confined to a specific subset of recipient domains. The blocks are variation of the following: 550 5.7.511 Access denied, banned sender[x.x.x.x]. To request removal from this list please forward this message to delist@microsoft.com. For more information please go to http://go.microsoft.com/fwlink/?LinkId=526653. AS(1410) Microsoft status page is reporting all systems are operational https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect Impacted users can submit delisting requests per the instructions provided by Microsoft by sending an email with a copy of the error message, and the blocked IP address, to "delist@microsoft.com". Delivery to Microsoft Outlook Consumer ("OLC"), for domains such as 'hotmail.com', 'outlook.com', etc., does not appear to be impacted. We will be monitoring and providing updates as new information becomes available.

    provider

  2. monitoring

    We are continuing to monitor for any further issues.

    provider

  3. monitoring

    We are seeing reduction in block rates and some customers are indicating improvements. We will continue to monitor for any further updates.

    provider

  4. resolved

    The incident is resolved and block rates are back to normal but customers will see change in block classifications from Microsoft 365. Users that continue to see elevated blocks can submit delisting requests to Microsoft by sending an email with a copy of the error message, and the blocked IP address, to "delist@microsoft.com". Delisting requests can also be made via the Office 365 Anti-Spam IP Delist Portal at https://sender.office.com/

    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-69fdf9cb3a

Is Twilio still down?

No, this incident was resolved 2026-08-15 02:05 UTC. For Twilio's live state, see https://down.guide/twilio.

How long did it last?

34m, from 2026-08-15 01:31 UTC to 2026-08-15 02:05 UTC, by the times Twilio posted.

What caused it?

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

Where does this come from?

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