CyberQP Outage History

CyberQP is up right now

There were 2 CyberQP outages since February 26, 2026 totaling 149h 23m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.getquickpass.com

Minor April 7, 2026

Admin Dashboard Slowness

Detected by Pingoru
Apr 07, 2026, 07:30 PM UTC
Resolved
Apr 13, 2026, 10:33 PM UTC
Duration
6d 3h
Affected: Web DashboardWeb DashboardWeb Dashboard
Timeline · 5 updates
  1. investigating Apr 07, 2026, 07:30 PM UTC

    We are currently investigating reports of slowness affecting the CyberQP dashboard. Our team has been made aware of the issue and investigation is underway. We will provide further updates as more information becomes available.

  2. identified Apr 07, 2026, 08:22 PM UTC

    We have identified the cause of the Dashboard slowness and are working on mitigation.

  3. identified Apr 08, 2026, 10:23 PM UTC

    Audit events performance is currently degraded. Our team is actively investigating and working to resolve the issue as quickly as possible.

  4. monitoring Apr 09, 2026, 06:32 PM UTC

    We have deployed a fix, and everything is operating normally. Our team will continue to monitor closely to ensure stability.

  5. resolved Apr 13, 2026, 10:33 PM UTC

    After monitoring over the weekend, we're seeing normal Dashboard responsiveness. This incident has been resolved.

Read the full incident report →

Major February 26, 2026

Entra M365 JIT Re-Enable - Password Incorrect

Detected by Pingoru
Feb 26, 2026, 10:57 PM UTC
Resolved
Feb 27, 2026, 01:18 AM UTC
Duration
2h 20m
Affected: Just In Time/Passwordless FunctionalityJust In Time/Passwordless FunctionalityJust In Time/Passwordless Functionality
Timeline · 4 updates
  1. investigating Feb 26, 2026, 10:57 PM UTC

    We are currently investigating an issue affecting Entra/M365 Just in Time (JIT) accounts that have been re-enabled after a period of being disabled. In this state, the password displayed by the Dashboard and Chrome Extension does not match the active credential, preventing successful login. Active Directory and Local JIT accounts are not affected. New Entra/M365 JIT account creation also continues to function normally. Workaround: Deleting the affected JIT account and recreating it from scratch will resolve the issue. Please note this will require the end user to re-register MFA. We recommend evaluating the impact of MFA re-registration in your environment before proceeding. Our team is treating this as the highest priority and is actively working toward a resolution.

  2. identified Feb 27, 2026, 12:20 AM UTC

    We have identified the likely cause: a synchronization delay on the Microsoft Entra/M365 side. Waiting approximately 5 minutes after re-enabling a Just in Time account will allow login with the supplied password. We are continuing to investigate whether this delay can be reduced on our end, or whether it is inherent to Microsoft's platform. Further updates to follow.

  3. resolved Feb 27, 2026, 01:18 AM UTC

    We’ve completed our review of the reported login delays impacting Just-in-Time (JIT) accounts. Our investigation, including comparison of our activity logs with Microsoft Entra Audit Logs, confirms that credentials are being generated and delivered correctly at the time of activation. The delay is occurring between the password reset event and when the updated credentials become active within Entra/M365. We are continuing to monitor this behavior and will provide a further update once latency returns to expected levels.

  4. postmortem Mar 03, 2026, 07:31 PM UTC

    Although the root cause was not within our platform, the impact was material and we recognize the additional operational overhead this created for your team. We have now released an enhancement to the Microsoft Entra ID / Microsoft 365 Just in Time \(JIT\) integration that successfully works around the issue observed beginning February 26 at approximately 12:00 PM EST. **What This Means for You** ‌ **Currently Enabled Entra/M365 JIT Accounts** * No action is required. These accounts will function normally moving forward. ‌ **Currently Disabled Entra/M365 JIT Accounts** Action is required: * Re-enable the JIT account. * Using either the Chrome extension or the QTech Mobile application, extend the JIT duration. After this step is completed, all subsequent disable/re-enable cycles for that account will function normally without additional intervention. **Alternative Option** You may delete and recreate the JIT account. However, this will require the user to re-register MFA and may introduce additional administrative effort and delay.

Read the full incident report →

Looking to track CyberQP downtime and outages?

Pingoru polls CyberQP's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when CyberQP reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track CyberQP alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring CyberQP for free

5 free monitors · No credit card required