Company Logo

Is there an KnowBe4 outage?

KnowBe4 status: Systems Active

Last checked: 6 minutes ago

Get notified about any outages, downtime or incidents for KnowBe4 and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

KnowBe4 outages and incidents

Outage and incident data over the last 30 days for KnowBe4.

There have been 6 outages or incidents for KnowBe4 in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for KnowBe4

Outlogger tracks the status of these components for Xero:

Free Tools Active
KnowBe4.com Active
KnowBe4 Community Active
Phish Alert Button Active
Support.KnowBe4.com Active
Console Active
Account Settings Active
Account Settings Active
API Active
Audit Log Active
Console Active
Email Delivery Active
Learner Experience (LX) Active
ModStore Active
Phishing Active
PIQ Active
Reporting Active
Training Active
User Provisioning Active
Console Active
Inbox Active
Integrations Active
Notification Service Active
PhishML Active
PhishRIP Active
Rooms Active
Webhooks Active
Coaching Delivery Active
Console Active
Real-Time Coaching Campaigns Active
Security Vendor Integration Service Active
User Mapping Engine Active
Component Status
Free Tools Active
KnowBe4.com Active
KnowBe4 Community Active
Phish Alert Button Active
Support.KnowBe4.com Active
Active
Console Active
Active
Account Settings Active
Account Settings Active
API Active
Audit Log Active
Console Active
Email Delivery Active
Learner Experience (LX) Active
ModStore Active
Phishing Active
PIQ Active
Reporting Active
Training Active
User Provisioning Active
Active
Console Active
Inbox Active
Integrations Active
Notification Service Active
PhishML Active
PhishRIP Active
Rooms Active
Webhooks Active
Active
Coaching Delivery Active
Console Active
Real-Time Coaching Campaigns Active
Security Vendor Integration Service Active
User Mapping Engine Active

Latest KnowBe4 outages and incidents.

View the latest incidents for KnowBe4 and check for official updates:

Updates:

  • Time: Sept. 6, 2024, 2:41 p.m.
    Status: Postmortem
    Update: On Thursday, August 16, 2024, from approximately 3:17 p.m. to 3:45 p.m. \(UTC\), some customers were unable to access their Account Settings in the KnowBe4 console. This incident was caused by a configuration change to a backend database. During the update, two fields with a null value caused errors when they were searched for. Another update was deployed to account for the null values and the console returned to regular performance by 3:45 p.m. No data loss occurred as a result of this issue.
  • Time: Aug. 16, 2024, 5:10 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Aug. 16, 2024, 3:53 p.m.
    Status: Monitoring
    Update: We’ve implemented a fix for the issue with the KSAT account settings and we’re monitoring the results to make sure no further issues occur.
  • Time: Aug. 16, 2024, 3:27 p.m.
    Status: Identified
    Update: We have identified an issue with KSAT account settings not loading and we are working on implementing a fix. We'll update our status page with any new information or updates.

Updates:

  • Time: Sept. 6, 2024, 2:09 p.m.
    Status: Postmortem
    Update: On Thursday, August 15, 2024, from approximately 6:10 p.m. to 7:08 p.m. \(UTC\), some US customers were unable to log in to their KnowBe4 console. This incident was caused by a third-party vendor update. An Amazon Web Services \(AWS\) planned configuration change increased API error rates for the KnowBe4 console. An AWS rollback was automatically triggered at 6:17 p.m. and service was fully restored by 7:08 p.m. For more information, see [Amazon’s AWS Service History post on their website](https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-east-1::event/SQS/AWS_SQS_OPERATIONAL_ISSUE/AWS_SQS_OPERATIONAL_ISSUE_7AB2F_D2A7D1D0D34). No data loss occurred as a result of this issue.
  • Time: Aug. 16, 2024, 12:38 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Aug. 15, 2024, 8:10 p.m.
    Status: Monitoring
    Update: The issues with KSAT console logins and 500 errors have been resolved. We're monitoring the results to make sure no further issues occur.
  • Time: Aug. 15, 2024, 6:47 p.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: Aug. 15, 2024, 6:43 p.m.
    Status: Investigating
    Update: We have identified an issue with KSAT console logins and 500 errors. We are working on implementing a fix and we'll update this page with any new information or updates.

Updates:

  • Time: Aug. 29, 2024, 4:47 p.m.
    Status: Postmortem
    Update: On Monday, August 5th, 2024, from approximately 6:05 p.m. until August 6th, 2024, at 2:05 p.m. \(UTC\), some customers on the EU instance of the KSAT console experienced issues with starting campaigns, generating reports, adding users to campaigns, and mapping users in SecurityCoach. This incident was caused by an update to resolve the prior incident [KSAT - Campaign Delays](https://status.knowbe4.com/incidents/2dy7trnhx6s2) that occurred on August 5th, 2024. This update caused the affected tasks to appear to be successful in the backend despite not completing. Another update was deployed to address the issue and restart the processes. The console returned to regular performance by 2:05 p.m on August 6th, 2024. To prevent this type of issue in the future, we have enhanced our logging and monitoring capabilities to allow for improved visibility into our task processing.
  • Time: Aug. 6, 2024, 5:11 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Aug. 6, 2024, 12:33 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: Aug. 6, 2024, 12:32 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.
  • Time: Aug. 6, 2024, noon
    Status: Investigating
    Update: We have received reports that campaigns are delayed, as well as reports about other issues with KSAT and SecurityCoach. We are looking into these reports and will update this page when we have more information.

Updates:

  • Time: Aug. 12, 2024, 3:39 p.m.
    Status: Postmortem
    Update: On Monday, 08/05/2024, from approximately 3:45 p.m. until 5:50 p.m. \(UTC\), all instances of the KSAT console experienced delays with training and phishing campaigns. This incident was caused when we deployed an update to the database access layer for one of our services. The update unexpectedly prevented some background jobs from completing successfully. While we manually implemented some mitigation steps, the US instance of the KSAT console also experienced approximately 15 minutes of downtime. Once the update finished deploying, KSAT was able to return to normal performance by 5:50 p.m. \(UTC\). Any jobs that failed to process during the deployment were able to be completed successfully after the deployment was completed. To prevent this type of issue in the future, we made adjustments to our updating and testing processes. We also completed additional, after-hours maintenance on the remaining environments on Thursday, 08/08/2024, at 1 a.m. \(UTC\). No data loss occurred as a result of this issue.
  • Time: Aug. 5, 2024, 8:05 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Aug. 5, 2024, 6:05 p.m.
    Status: Monitoring
    Update: The US instance of the KSAT web console experienced approximately 15 minutes of downtime while we implemented the fix for the previous issue. This issue has been mitigated as well. No additional issues are expected from this incident. Some after-hours maintenance will be performed this Wednesday at 9pm EDT to reconcile some other components of this release.
  • Time: Aug. 5, 2024, 5:11 p.m.
    Status: Monitoring
    Update: We’ve implemented a fix for the issue causing delays in the KSAT console, and we’re monitoring the results to make sure no further issues occur.
  • Time: Aug. 5, 2024, 4:30 p.m.
    Status: Identified
    Update: We've identified the cause of an issue causing delays with training and phishing campaigns in the KSAT console. We are implementing a fix, and we'll continue to post on our status page with any new information or updates.

Updates:

  • Time: Aug. 2, 2024, 5:56 p.m.
    Status: Postmortem
    Update: On Tuesday, 07/30/2024, from approximately 9:56 p.m. to Wednesday, 07/31/2024 at 2:20 a.m. \(UTC\), all of KnowBe4's products on the US instance experienced elevated error rates and intermittent service disruption. This incident was caused by an unexpected technical issue that impacted many of our systems. The disruption began to recover around Wednesday, 07/31/2024, at 1:47 a.m. \(UTC\), KnowBe4's products were able to return to normal performance by 2:20 a.m. \(UTC\) No data loss occurred as a result of this issue.
  • Time: July 31, 2024, 1:39 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: July 31, 2024, 2:50 a.m.
    Status: Monitoring
    Update: At 2:20am UTC, our error rate returned to normal. It has remained low for 30 minutes, and we have seen signs of all impacted features and services reaching or nearing a full recovery. We will leave this incident in Monitoring status for the next few hours as we continue to ensure the health of our products and features.
  • Time: July 31, 2024, 2:29 a.m.
    Status: Identified
    Update: We are seeing good signs of recovery and a significant reduction in our error rate. Most delayed background jobs were able to process successfully around 2:00 UTC. We are still working towards a full recovery.
  • Time: July 31, 2024, 1:28 a.m.
    Status: Identified
    Update: We are continuing to work on resolving this incident. Some services are showing early signs of recovery, though we are still experiencing elevated error rate. Most background jobs are still processing successfully with some elevated delays or latency.
  • Time: July 31, 2024, 12:15 a.m.
    Status: Identified
    Update: We have identified the cause of this incident, and we are continuing to investigate the scope of this issue.
  • Time: July 30, 2024, 11:21 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.
  • Time: July 30, 2024, 11:10 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.

Check the status of similar companies and alternatives to KnowBe4

Intapp
Intapp

Systems Active

Aderant
Aderant

Systems Active

Springbrook
Springbrook

Systems Active

Sumsub
Sumsub

Systems Active

AgentSync
AgentSync

Systems Active

MyCase - Public
MyCase - Public

Systems Active

Litify
Litify

Systems Active

Evotix
Evotix

Systems Active

Penneo A/S
Penneo A/S

Systems Active

Casetext
Casetext

Systems Active

FOSSA
FOSSA

Systems Active

Frequently Asked Questions - KnowBe4

Is there a KnowBe4 outage?
The current status of KnowBe4 is: Systems Active
Where can I find the official status page of KnowBe4?
The official status page for KnowBe4 is here
How can I get notified if KnowBe4 is down or experiencing an outage?
To get notified of any status changes to KnowBe4, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of KnowBe4 every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does KnowBe4 do?
KnowBe4 offers Security Awareness Training to address IT security challenges such as social engineering, spear phishing, and ransomware attacks.