← Back to Twilio History
none✓ Resolved

Widespread Microsoft 365 IP Block Causing Delivery Failures for Multiple Users

Twilio•
Status
resolved
Duration
34m
Updates
4
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
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/
monitoring
We are seeing reduction in block rates and some customers are indicating improvements. We will continue to monitor for any further updates.
monitoring
We are continuing to monitor for any further issues.
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.

📊 TECHNICAL DETAILS

Internal ID
14d9be92-286b-41f6-87f9-abacd488fcdf
External ID
f8vsxj0hk5by
🕐 Started
🔄 Last Updated
✓ Resolved
NONE
Impact Level
34m
Total Duration
4
Status Updates
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed