KnowBe4 experienced a minor incident on September 17, 2025 affecting Phishing, lasting 6d 1h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Sep 17, 2025, 06:17 PM UTC
We are currently investigating a delay in phishing campaigns starting.
- monitoring Sep 19, 2025, 01:29 PM UTC
We’ve implemented a fix for the delayed phishing campaigns and we’re monitoring the results to make sure no further issues occur.
- resolved Sep 23, 2025, 07:30 PM UTC
This incident has been resolved.
- postmortem Oct 03, 2025, 07:29 PM UTC
On Wednesday, September 17, 2025, from approximately 12:57 p.m. to 4:21 p.m. \(UTC\), some customers experienced delayed phishing campaign starts and instances of phishing campaigns not including all assigned users. These issues were caused by unusually high traffic in the KSAT console, leading to delays for phishing campaigns. To resolve this issue, we improved our code to process phishing campaign queries more efficiently and relieve pressure on the database. The KSAT console returned to normal performance by 4:21 p.m. \(UTC\). To prevent this type of issue in the future, our code improvements will allow for better handling of phishing campaign queries during periods of high traffic. No data was lost as a result of this issue. Many accounts created duplicate phishing campaigns during this incident. To avoid users receiving duplicate phishing campaign tests, we did not automatically add users back to affected phishing campaigns. If you experienced an instance of a phishing campaign not including all assigned users, we recommend duplicating the original campaign, creating a [Smart Group](https://support.knowbe4.com/hc/en-us/articles/8354913796115-Smart-Groups-Overview) for the missing users, and then including only that Smart Group in the new campaign. For further information, please contact our support team at [support.knowbe4.com](http://support.knowbe4.com).