Resolved after 6 hours 17 minutes, affecting Shield, on October 20, 2026.
The queues are caught up, and we are observing normal mail flow at this time. The rate limiting experienced this morning was a response to abusive mail volume that was exacerbated by the reduction in Microsoft servers communicating with Shield. We will continue to monitor our queues through the business day to ensure processing is stable.
Affected components
Update timeline
- investigating Oct 20, 2026, 04:32 PM UTC
We are investigating reports of connection timeouts or rate limiting with some domains using Shield. This is not affecting all mail flow.
- investigating Oct 20, 2026, 05:21 PM UTC
We are continuing to investigate this issue.
- identified Oct 20, 2026, 06:21 PM UTC
It appears that a reduction in the number of Microsoft servers communicating with Shield this morning contributed to the per-server volume spike. The team has mitigated the connection timeouts and rate limits, and the queues are draining. We do not have an exact time for when the queues will be emptied, but it appears it should be within the hour, most likely sooner. We are continuing to investigate with a priority of restoring stable and expected mail flow.
- monitoring Oct 20, 2026, 06:55 PM UTC
The queues are caught up, and we are observing normal mail flow at this time. The rate limiting experienced this morning was a response to abusive mail volume that was exacerbated by the reduction in Microsoft servers communicating with Shield. We will continue to monitor our queues through the business day to ensure processing is stable.
- resolved Oct 20, 2026, 10:50 PM UTC
This incident has been resolved.
Your product runs on more than mailprotector
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services