PhishER - PhishML Issues (US Only)

Incident Report for KnowBe4

Postmortem

From Tuesday, August 28, 2024, at approximately 8:50 p.m. until Thursday, August 29, 2024 at approximately 3:44 p.m. (UTC), some customers experienced an issue with their PhishML queries not processing.

This incident was caused by the removal of legacy code that was still used by a connected service. This issue was mitigated when the code was restored at approximately 10:00 p.m on August 28, 2024 and the console returned to regular performance by 3:44 p.m. on August 29, 2024.

To prevent this issue in the future, we have implemented automated monitoring for the affected service and we are reviewing a larger scope of services when removing legacy code.

No data loss occurred as a result of this issue.

Posted Sep 16, 2024 - 19:38 UTC

Resolved

This incident has been resolved.

Posted Aug 29, 2024 - 15:35 UTC

Monitoring

We’ve implemented a fix for the PhishER PhishML issues, and we’re monitoring the results to make sure no further issues occur.

Posted Aug 28, 2024 - 22:48 UTC

Identified

We've identified the cause of the PhishER PhishML issues and we are working on implementing a fix. We'll update our status page with any new information or updates.

Posted Aug 28, 2024 - 21:59 UTC

Investigating

We have received reports that PhishML is not processing new messages. We are investigating this issue and will update this page when we have more information.

Posted Aug 28, 2024 - 21:33 UTC

This incident affected: PhishER (Console, PhishML).