- Level
- confirmed
- Worst impact
- Maintenance
- Components
- API v3
What to do
Check whether you use Twilio API v3. 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.Check that everything you run on Twilio came back after the window closed 2026-09-04 18:56 UTC.
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 6
- 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.
provider
- 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.
provider
- 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
provider
- monitoring
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
provider
- monitoring
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
provider
- 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.
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-8471ea788b
Is this Twilio maintenance still going on?
No, it ended 2026-09-04 18:56 UTC.
How long did it last?
5h 57m, from 2026-09-04 12:59 UTC to 2026-09-04 18:56 UTC, by the times Twilio posted.
What was affected?
Twilio named API v3.
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.