Scheduled maintenance
Twilio Services
Issues related to Twilio’s Software
External Connectivity
Issues found outside of Twilio’s Network
Zipwhip Gateway
Issues related to Zipwhip's Services
System Metrics
Multiple delivery failures when sending emails to Microsoft or MS based recipients
Incident
Report for Twilio
Resolved
Our engineers have monitored the issue and confirmed the issue with email deliveries to Microsoft has recovered to normal levels. All services are now operating normally at this time.
Update
We are continuing to seeing a recovery in our services for customer sending to Microsoft and MS 365 supported recipients, and we'll continue to monitor. Microsoft has acknowledged this issue here: https://x.com/MSFT365Status and we kindly ask our customers to reach out to them for more updates
We'll provide more updates in 3 hours or as soon as they become available
We'll provide more updates in 3 hours or as soon as they become available
Update
We are continuing to seeing a recovery in our services for customer sending to Microsoft and MS 365 supported recipients, and we'll continue to monitor. Microsoft has acknowledged this issue here: https://x.com/MSFT365Status and we kindly ask our customers to reach out to them for more updates
We'll provide more updates in 2 hours or as soon as they become available
We'll provide more updates in 2 hours or as soon as they become available
Monitoring
We are seeing a recovery in our services for customer sending to Microsoft and MS 365 supported recipients, and we'll continue to monitor. Microsoft has acknowledged this issue here: https://x.com/MSFT365Status and we kindly ask our customers to reach out to them for more updates
We'll provide more updates in 2 hours or as soon as they become available
We'll provide more updates in 2 hours or as soon as they become available
Identified
Our engineers have identified the cause of the incident to be a change in the delivery policies with Microsoft as it has been acknowledged on their status post here: https://x.com/MSFT365Status.
We encourage the customers to reach out to them directly for more information and updates including the affected IP and the exact message received.
Errors such as "IPs throttled by recipient server" is a preemptive deferral in response to the "Server too busy" error, so we suggest that all errors should be read as literal and reach out Microsoft if you need more details on this: https://olcsupport.office.com/, and for Office 365 Anti-Spam IP delisting portal here: https://sender.office.com/ and their address for delisting is delist@microsoft.com.
We will provide another update in 2 hours or as soon as more information becomes available.
We encourage the customers to reach out to them directly for more information and updates including the affected IP and the exact message received.
Errors such as "IPs throttled by recipient server" is a preemptive deferral in response to the "Server too busy" error, so we suggest that all errors should be read as literal and reach out Microsoft if you need more details on this: https://olcsupport.office.com/, and for Office 365 Anti-Spam IP delisting portal here: https://sender.office.com/ and their address for delisting is delist@microsoft.com.
We will provide another update in 2 hours or as soon as more information becomes available.
Investigating
Starting around 3:30 PST on September the 4th, our engineers began investigating an issue with all emails being delivered to Microsoft. Users may experience different 5XX errors such as:
Email was deferred due to the following reason(s): [IPs were throttled by recipient server:
Mail send is affected only when sending to Microsoft supported services We will provide another update in an hour or as soon as more information becomes available.
Email was deferred due to the following reason(s): [IPs were throttled by recipient server:
Mail send is affected only when sending to Microsoft supported services We will provide another update in an hour or as soon as more information becomes available.
This incident affected: SendGrid Mail Sending (API v3).