mailprotector Outage History

The AWS outage has been resolved, and CloudFilter's impact has been minimal. Quarantine access and performance are operational.

AWS has confirmed the issue with S3 storage has been resolved.

From approximately 3:35 PM ET outgoing emails were being held for review at an aggressive rate. The team was alerted and resolved the verification rule causing the aggressive filtering about an hour later. Emails sent during this time will need to be released by the sender. Senders will have received a notification stating their email(s) been held for review and clicking the release button will deliver the message to the intended recipient(s).

Link analysis has been modified to improve performance and X-ray should be working as expected.

This incident has been resolved.

This incident has been resolved.

On July 25, 2024, between approximately 5:30 PM ET and 7:00 PM ET, DMARC results with a reject policy were sent to quarantine rather than bounced as per RFC. This temporary change was made after reports of false DMARC failures. The team evaluated the logs and spotted intermittent SPF failures in the DMARC evaluation process. An adjustment was applied to eliminate the SPF check failure. As of 7:00 PM ET, a failed DMARC with a reject policy has resumed bouncing those emails. Evidence of emails bounced due to a sending domain's DMARC policy will be found in the logs. NOTE: A DMARC policy is set by the owners of the sending domain, not Mailprotector or a recipient. If the policy is set to reject messages that fail DMARC alignment, the bounce is made regardless of Allow rules.

From approximately 3:40 PM ET, manager accounts could not log into emailservice.io or partner-branded URLs. The team resolved the issue, and manager logins are confirmed to be working as of 5:15 PM ET. Thank you.