KnowBe4 incident

Defend - Sending multiple abuse mailbox submission notifications

Minor Resolved View vendor source →
Started
Mar 31, 2026, 03:13 PM UTC
Resolved
Mar 31, 2026, 04:45 PM UTC
Duration
1h 32m
Detected by Pingoru
Mar 31, 2026, 03:13 PM UTC

Affected components

Mail Flow

Update timeline

  1. identified Mar 31, 2026, 03:13 PM UTC

    We've identified some users are receiving multiple abuse mailbox submissions. We've identified a fix which should resolve the issue.

  2. monitoring Mar 31, 2026, 03:19 PM UTC

    We've implemented a fix and are continuing to monitor to ensure this is resolved

  3. resolved Mar 31, 2026, 04:45 PM UTC

    This incident has been resolved.

  4. postmortem Apr 01, 2026, 09:42 PM UTC

    On Tuesday, March 31, 2026, from approximately 15:00 \(UTC\) to 16:10 \(UTC\), some users experienced issues with the Defend Abuse Mailbox service. This incident was caused by a service update that started sending duplicate phishing submission notifications to users. To resolve this issue, we corrected the service update code that caused the duplicate notifications, and the Defend Abuse Mailbox service returned to normal performance by 16:10 \(UTC\). To prevent this type of issue in the future, we are reviewing and improving our service upgrade workflow. No data loss occurred as a result of this issue.

Looking to track KnowBe4 downtime and outages?

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

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

5 free monitors · No credit card required