Completed -
The scheduled maintenance has been completed.
Jun 26, 02:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 26, 01:00 UTC
Scheduled -
We will be performing maintenance work on all instances on June 26th, 2026 from 01:00 AM UTC to 02:00 AM UTC. During this maintenance window users may experience elevated latency or transient slowness with membership updates such as adding or removing users to or from groups.
Jun 24, 20:23 UTC
Resolved -
We have identified an issue where users may receive a 500 error upon logging into KCM GRC. A fix has been implemented, and users should be able to login without error.
Jun 25, 13:10 UTC
Monitoring -
We have identified an issue where users may receive a 500 error upon logging into KCM GRC. A fix has been implemented, and we will continue to monitor this issue.
Jun 24, 22:06 UTC
Investigating -
We have identified an issue where users may receive a 500 error upon logging into KCM GRC, and our engineering team is looking into a fix.
Jun 24, 15:48 UTC
Resolved -
This incident has been resolved.
Jun 19, 14:01 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jun 18, 22:42 UTC
Update -
We are continuing to investigate this issue.
Jun 18, 21:16 UTC
Investigating -
We have received reports of the Phishing test reports tab currently being unavailable. We are investigating this issue and will update this page when we have more information.
Jun 18, 21:14 UTC
Resolved -
This incident has been resolved.
Jun 18, 19:12 UTC
Monitoring -
We’ve implemented a fix for the Human Risk Management widget and we’re monitoring the results to make sure no further issues occur.
Jun 18, 15:43 UTC
Investigating -
We have received reports that the Human Risk Managment widget is showing no results in the KnowBe4 Security Center. We are investigating this issue and will update this page when we have more information.
Jun 18, 15:13 UTC
Resolved -
This incident has been resolved.
Jun 17, 20:19 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jun 17, 12:48 UTC
Investigating -
We've identified an issue that has resulted in inconsistent reporting, and our engineering team is looking into a fix.
Jun 16, 22:23 UTC