Is KnowBe4 down?

Last checked just now
Current status
KnowBe4 is up

No incidents right now.

Official status page: https://status.knowbe4.com · Polled every 5 minutes · 44 components tracked

KnowBe4 is operational right now. Last checked just now; the most recent incident resolved 5d ago.

Real-time KnowBe4 status, recent outages, and incident history — pulled directly from KnowBe4's official status page at https://status.knowbe4.com every 5 minutes. Pingoru tracks 44 KnowBe4 services and has captured 32 incidents in the last 90 days (99.30% uptime). Get email, Slack, Discord, or webhook alerts the moment KnowBe4 reports a new incident — free for 5 monitors, no credit card.

Users who monitor KnowBe4 also follow these Security services: Duo Security LastPass 1Password Barracuda Rapid7 Palo Alto Networks Incapsula SentinelOne Keeper Canary View all 6,000+ providers
KnowBe4 uptime 99.30% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Sep 11, 2026, 12:43 PM UTC · Resolved Sep 08, 2026, 07:00 AM UTC
    Timeline · 1 update
    • resolved · Sep 11, 2026, 12:43 PM UTC

      On Septermber 8th we made aware that inbound HTML emails rendered partially or blank in Classic Outlook due to a routine HTML library upgrade in Defend's harmful-code-removal engine interacting with Classic Outlook's legacy Word rendering engine. New Outlook and Outlook on the web were unaffected. This was strictly a display issue: no email was delayed, lost, or compromised, and threat detection remained fully active. Engineering has reverted the update to restore normal rendering. If you temporarily disabled harmful-code removal during this window, please re-enable it to ensure complete protection.

    Latest: On Septermber 8th we made aware that inbound HTML emails rendered partially or blank in Classic Outlook due to a routine HTML library upgrade in Defend's harmful-code-removal engin…

  2. Resolved 2d 21h
    Started Sep 04, 2026, 10:53 AM UTC · Resolved Sep 07, 2026, 08:25 AM UTC
    Secure Workspace
    Timeline · 3 updates
    • investigating · Sep 04, 2026, 10:53 AM UTC

      We have received reports of an issue with delivery of Email verification MFA for Workspace. We are investigating this issue and will update this page when we have more information.

    • monitoring · Sep 04, 2026, 02:24 PM UTC

      We have received reports that the issue with delivery of Email verification MFA for Workspace has been mitigated by Microsoft, and we are monitoring the results.

    • resolved · Sep 07, 2026, 08:25 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 3h 31m
    Started Aug 26, 2026, 04:19 PM UTC · Resolved Aug 26, 2026, 07:51 PM UTC
    Inbox
    Timeline · 3 updates
    • investigating · Aug 26, 2026, 04:19 PM UTC

      We have identified an issue where users may experience delays in messages being processed, and our engineering team is looking into a fix.

    • monitoring · Aug 26, 2026, 04:46 PM UTC

      Our engineering team has implemented a fix for the issue that causing message processing delays in PhishER, and we are monitoring the results.

    • resolved · Aug 26, 2026, 07:51 PM UTC

      Our engineering team has implemented a fix for the issue that causing message processing delays in PhishER.

    Latest: Our engineering team has implemented a fix for the issue that causing message processing delays in PhishER.

  4. Resolved 6h 4m
    Started Aug 21, 2026, 08:52 AM UTC · Resolved Aug 21, 2026, 02:57 PM UTC
    Phish Alert Button
    Timeline · 5 updates
    • investigating · Aug 21, 2026, 08:52 AM UTC

      We have received reports that the Gmail Phish Alert Button shows the error "[reportPhishAttempt()] An internal error has occurred. Please try again." when reporting phish. We are investigating this issue and will update this page when we have more information.

    • identified · Aug 21, 2026, 12:03 PM UTC

      The issue has been identified and a fix is being implemented.

    • monitoring · Aug 21, 2026, 01:08 PM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Aug 21, 2026, 02:57 PM UTC

      This incident has been resolved.

    • postmortem · Aug 26, 2026, 03:55 PM UTC

      On Friday, August 21, 2026, from approximately 05:20 to 12:55 \(UTC\), some customers experienced intermittent failures when using the Gmail Phish Alert Button add-in to report suspicious emails, receiving the "An internal error has occurred" message instead of a successful report confirmation. The issue affected customers across all regions, with the highest error volumes concentrated in the EU-West and US-East service regions. This issue was caused by a disruption in a caching service on Google's Apps Script platform, which the add-in relies on to store per-user session configuration. The service began intermittently returning empty results on read while still accepting new writes, causing affected report submissions to fail. KnowBe4 engaged Google directly and filed a formal bug report between approximately 12:19 and 12:39 \(UTC\). Error volume declined sharply shortly after as the vendor-side condition cleared, and the Gmail Phish Alert Button returned to normal performance by approximately 12:55 \(UTC\). To prevent this type of issue in the future, we are continuing to work with Google to track the resolution of the underlying caching defect. No data loss occurred as a result of this issue.

    Latest: On Friday, August 21, 2026, from approximately 05:20 to 12:55 \(UTC\), some customers experienced intermittent failures when using the Gmail Phish Alert Button add-in to report sus…

  5. Resolved 5h 44m
    Started Aug 18, 2026, 02:29 PM UTC · Resolved Aug 18, 2026, 08:14 PM UTC
    Phish Alert Button
    Timeline · 3 updates
    • investigating · Aug 18, 2026, 02:29 PM UTC

      We are investigating an issue causing a Non-Delivery Report (NDR) to be returned when a message is reported via the Phish Alert Button and "Send Us a Copy" is enabled in Account Settings

    • monitoring · Aug 18, 2026, 03:26 PM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Aug 18, 2026, 08:14 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

See the full KnowBe4 outage history

15 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse KnowBe4 outage history →

Or sign up free to get alerts when KnowBe4 breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 20 incidents View full outage history →