mailprotector incident

Virus scans in CloudFilter were unable to complete

Notice Resolved View vendor source →
Started
May 01, 2026, 04:52 PM UTC
Resolved
May 01, 2026, 03:00 PM UTC
Duration
Detected by Pingoru
May 01, 2026, 04:52 PM UTC

Update timeline

  1. resolved May 01, 2026, 04:52 PM UTC

    This morning, a third-party package repository used by our virus scanning infrastructure experienced an outage following an attack on its systems. Because our virus scanning instances rely on this repository at startup to pull the latest files and configurations, affected instances were unable to start. This reduced the capacity of our virus-scanning cluster below demand. When a virus scan cannot complete, our system quarantines the email as a precaution. As a result, emails processed during this window were quarantined rather than delivered to inboxes. No emails were lost. Affected emails can be released from quarantine by users or admins. Resolution The virus scanning cluster has been reconfigured to pull packages directly from the source repository, eliminating the dependency on the third-party intermediary. Monitoring and alerting thresholds have also been updated to surface this class of issue more quickly in the future. The issue is fully resolved.

Looking to track mailprotector downtime and outages?

Pingoru polls mailprotector's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when mailprotector reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track mailprotector alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring mailprotector for free

5 free monitors · No credit card required