HYPR Outage History

Started Feb 27, 2026, 02:11 PM UTC· resolved Feb 27, 2026, 03:42 PM UTC

1. investigating Feb 27, 2026, 02:11 PM UTC

   We are currently experiencing an issue with respect to Affirm Verification Flows pertaining to the Video Conversations.

2. investigating Feb 27, 2026, 02:12 PM UTC

   We are continuing to investigate this issue.

3. investigating Feb 27, 2026, 03:21 PM UTC

   We are continuing to investigate this issue.

4. resolved Feb 27, 2026, 03:42 PM UTC

   Following a review of the error logs, HYPR determined the root cause was exceeding the Twilio user conversation limit during the Affirm approval flow. This occurred because existing Affirm approval conversations remained open over time, eventually reaching the conversation threshold and preventing new approval flows from completing. All impacted conversations have now been successfully closed, and new Affirm flows have been tested and confirmed to run as expected. The issue was fully resolved by the end of the incident call, and all systems are currently functioning normally. We have implemented corrective measures and are putting additional safeguards in place to prevent this from recurring. Our team will continue to monitor the environment closely. If you have any further questions, please contact HYPR Support or your Customer Success Manager.

Read the full incident report →

Started Feb 23, 2026, 08:24 PM UTC· resolved Mar 13, 2026, 05:52 PM UTC

1. identified Feb 23, 2026, 08:24 PM UTC

   Workforce Access Clients are currently unavailable for download via Control Center. Please reach out to HYPR Support for alternative download methods. https://support.hypr.com/

2. identified Feb 23, 2026, 08:25 PM UTC

   Fix identified. Working on rollout plans.

3. resolved Mar 13, 2026, 05:52 PM UTC

   HYPR has resolved the underlying issue effecting Workforce Access downloads via Control Center.

Read the full incident report →

Started Jan 14, 2026, 07:51 PM UTC· resolved Jan 15, 2026, 08:16 PM UTC

1. monitoring Jan 14, 2026, 07:51 PM UTC

   We have become aware of a potential service issue affecting Affirm workflows that include SMS or voice-based phone verification steps. Verizon has reported a network outage that may result in delayed or failed delivery of one-time passcodes (OTPs) sent to end users on the Verizon carrier network. As a result, some users may be unable to successfully complete Affirm Identity Verification workflows that rely on phone verification during this time. What you may experience: - Delayed or failed SMS or voice OTP delivery to Verizon numbers - Increased verification failures or user drop-off at the phone verification step What HYPR is doing: - Our team is actively monitoring the situation to track Verizon’s recovery progress. - We will provide updates as more information becomes available. What you can do: - If possible, consider temporarily disabling phone-based verification steps or enabling alternate verification methods within your workflows. - Advise impacted end users to retry their verification later. We apologize for any inconvenience this may cause and appreciate your patience while Verizon works to restore service. Please reach out to HYPR Support if you have any questions or need assistance adjusting your workflows.

2. monitoring Jan 15, 2026, 05:12 AM UTC

   Verizon reports that their services have been restored and that devices still encountering issues should be restarted. If users continue to have issues with Affirm SMS messages after restarting their devices please reach out to our support team for further assistance.

3. resolved Jan 15, 2026, 08:16 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 14, 2026, 07:37 PM UTC· resolved Feb 27, 2026, 02:06 PM UTC

1. identified Jan 14, 2026, 07:37 PM UTC

   Problem Statement: Some users upgrading to HYPR version 10.7, on iOS experienced a loss of existing HYPR registrations,making them unable to authenticate to their accounts. Impacted users are able to successfully re register on the same device without issue as a workaround. Corrective Action: We have paused the rollout of the iOS 10.7 release. As a result, iOS devices will no longer automatically update to this version. Users may still manually update if they choose to do so, however it is not advised at this time. Our engineering team is actively working on a patch release and is prioritizing a near term resolution. The updated version will be submitted to the App Store as soon as it is ready. This page wil lbe updated once app store submission occurs.

2. monitoring Jan 15, 2026, 04:04 AM UTC

   Good Evening, We have released a new version of the HYPR app for iOS to the App Store, (Version 10.7.3). We recommend that all iOS users update to the latest version as the update includes important fixes that address the issue observed, and identified in HYPR's previous version (10.7.0 iOS). Our team will continue to monitor the rollout and overall application performance. Please contact HYPR Support if you experience any issues after updating or have additional questions Thank you, HYPR Support Team

3. resolved Feb 27, 2026, 02:06 PM UTC

   HYPR app for iOS Version 10.7.3 confirms this fix. We recommend that all iOS users update to the latest version as the update includes important fixes that address the issue observed, and identified in HYPR's previous version (10.7.0 HYPR App for iOS)

Read the full incident report →

Started Oct 20, 2025, 06:57 PM UTC· resolved Oct 21, 2025, 01:27 PM UTC

1. identified Oct 20, 2025, 06:57 PM UTC

   HYPR Event Bridge for Webhooks Integration is currently experiencing an outage related to the ongoing AWS issues: https://health.aws.amazon.com/health/status . This may also impact the accuracy of certain metrics dashboards in the Control Center, due to data being delayed. HYPR Event Bridge depends upon impacted services in AWS. We are working with AWS to restore service ASAP. If you have any questions please contact support via the portal: https://csp.hypr.com

2. monitoring Oct 20, 2025, 08:01 PM UTC

   As of 3:30PM EDT we are seeing a return to normal traffic volume for the Event Bridge. We will continue to monitor this system closely and provide further updates if any issues arise.

3. monitoring Oct 20, 2025, 09:59 PM UTC

   Event Bridge continues to show normal traffic patterns since the previous update. We will continue to keep careful watch on our systems as well as the upstream services they depend on. Please continue to monitor this page for any further developments.

4. resolved Oct 21, 2025, 01:27 PM UTC

   After careful monitoring overnight, we are pleased to report all systems are operating normally following yesterdays outage of US East 1.

Read the full incident report →

Started Oct 20, 2025, 06:55 PM UTC· resolved Oct 21, 2025, 01:27 PM UTC

1. identified Oct 20, 2025, 06:55 PM UTC

   HYPR Affirm is currently experiencing an outage related to the ongoing AWS issues: https://health.aws.amazon.com/health/status . HYPR Affirm depends upon impacted services in AWS as well as other sub processors, who are also impacted by the AWS service disruption. We are working with AWS to restore service ASAP. If you have any questions please contact support via the portal: https://csp.hypr.com

2. identified Oct 20, 2025, 06:55 PM UTC

   We are continuing to work on a fix for this issue.

3. monitoring Oct 20, 2025, 09:58 PM UTC

   HYPR Affirm is functionaing normally as of 4:30 EDT and has remained stable for the past 90 minutes. We will continue to keep a vigilant watch on our systems and the upstream services on which they depend. Please continue to monitor this page for any further developments.

4. resolved Oct 21, 2025, 01:27 PM UTC

   After careful monitoring overnight, we are pleased to report all systems are operating normally following yesterdays outage of US East 1.

Read the full incident report →

Started Oct 20, 2025, 09:54 AM UTC· resolved Oct 21, 2025, 01:27 PM UTC

1. monitoring Oct 20, 2025, 09:54 AM UTC

   This morning at approximately 3:00 AM EDT HYPR Became aware of an issue with our upstream provider: AWS. (More info here: https://health.aws.amazon.com/health/status ). As a result several HYPR tenants in the impacted region experienced issues with authentication. Consequently, we also were unable to access this status page until moments ago. While AWS continues to work on fully resolving the issue, we have instrumented a workaround, and are closely monitoring tenant health.

2. monitoring Oct 20, 2025, 02:33 PM UTC

   As of 5:50 AM EDT, All affected HYPR Customer tenants are restored to normal service. Though all tenants are currently healthy, HYPR is continuing to actively monitor this incident vigilantly. HYPR is keeping a close watch on AWS status: https://health.aws.amazon.com/health/status for full recovery of their systems, before considering this incident closed. If you have any additional questions please reach out to HYPR Support via https://csp.hypr.com

3. monitoring Oct 20, 2025, 10:01 PM UTC

   All HYPR Authenticate/Control Center tenants have continued to operate normally throughout the day. We will continue to monitor them and their upstream services vigilantly. Please continue to monitor this page for any further updates.

4. resolved Oct 21, 2025, 01:27 PM UTC

   After careful monitoring overnight, we are pleased to report all systems are operating normally following yesterdays outage of US East 1.

Read the full incident report →

Started Oct 20, 2025, 07:00 AM UTC· resolved Oct 20, 2025, 07:00 AM UTC

1. resolved Oct 20, 2025, 09:51 AM UTC

   This morning at approximately 3:00 AM EDT HYPR Became aware of an issue with out our upstream provider AWS. (More info here: https://health.aws.amazon.com/health/status ). As a result several HYPR tenants in the impacted region experienced issues with authentication. Consequently, we also were unable to access this status page until moments ago. While AWS continues to work on fully resolving the issue, we have instrumented a workaround, and are closely monitoring tenant health.

Read the full incident report →

Started Sep 25, 2025, 05:49 PM UTC· resolved Oct 20, 2025, 09:45 AM UTC

1. identified Sep 25, 2025, 05:49 PM UTC

   We are publishing this notice regarding the rollout of one of our new features in our latest iOS release, Version 10.5.0. There is a new notification in iOS to enable one of the new features, which your end users may not expect. This notification would have potentially been seen by 2% of the total end user population during the first couple of hours of the rollout of 10.5.0, before HYPR noticed the issue and took action. We want to sincerely apologize for any confusion this may have caused. The feature in question, HYPR Enterprise Passkey for web and mobile, requires that end users enable the HYPR iOS application as a passkey provider. We understand that clear and accurate information is critical to your decision-making and day-to-day operations. Here’s what you need to know: *The intended functionality of the feature is a registered Enterprise Passkey in the HYPR Mobile App through the native passkey provider support in iOS, enabling native and browser mobile use cases. *Users are able to click on “Enable Provider” and there is no impact to the HYPR product functionality. *Users are able to click on “Cancel” and there is no impact to the HYPR product functionality if they do not leverage Enterprise Passkeys. *This Feature was meant to only be enabled at customers/admins discretion for use with Enterprise Passkey Functionality. However, due to a bug, this feature is affecting all iOS users who have the 10.5.0 release of the HYPR app. We have currently paused the rollout of the 10.5.0 release on iOS and are patching the current code to affect the correct behavior. We deeply regret any inconvenience this has caused and are also taking steps to ensure our future communications are more precise and informative. Your trust is extremely important to us, and we are dedicated to maintaining transparency with our valued customers. If you have any further questions or require assistance, please do not hesitate to contact our support team at the support portal https://csp.hypr.com or via email [email protected]. Thank you for your understanding and continued support.

2. resolved Oct 20, 2025, 09:45 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 12, 2025, 07:33 PM UTC· resolved Jun 13, 2025, 09:48 AM UTC

1. identified Jun 12, 2025, 07:33 PM UTC

   2 Upstreams service providers which HYPR Relies upon, or which individual HYPR customers may be integrated with are currently reporting issues impacting their services. HYPR has observed intermittent issues for end users of our service as a result. We will continue to monitor all three issues as they develop. https://status.firebase.google.com/incidents/YUxWS9naU43zfSvzA1i1 https://www.cloudflarestatus.com/

2. identified Jun 13, 2025, 12:07 AM UTC

   Our Upstream Service Providers report operation has been restored to their services, and HYPR observes a return to nominal error rates as a result. We are closing the incident for this issue but will be keeping a closer eye on our systems and upstream status reports for the rest of the weekend. If you observe any abnormal issues as always please feel free to contact Support.

3. resolved Jul 10, 2025, 09:48 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 21, 2025, 03:04 PM UTC· resolved Feb 13, 2025, 02:57 PM UTC

1. identified Jan 21, 2025, 03:04 PM UTC

   We’ve discovered a compatibility issue between Windows update KB5050008 (OS Build 17763.6775) and the HYPR Desktop Client when this Windows update is installed on domain controllers. This update seems to cause a problem with certificate authentication and can disrupt authentication and registration of HYPR for workstations. Please do not install this update on domain controllers, until HYPR is able to investigate further and advise on a solution; if already installed, contact HYPR Support immediately.

2. identified Jan 22, 2025, 03:44 PM UTC

   As we have continued to investigate this with customers we have determined that this issue is encountered across multiple versions of Windows Server by specific KB updates all pushed around the same time: server 2019: KB5050008 server 2022: KB5049983 Depending on your version of Windows Server you will need avoid or uninstall the associated Windows Updates to restore Certificate Authentication functionality if you have been impacted. The changes in these windows updates appear to cause a problem with Smart Card Authentication Certificates. We are currently engaged with Microsoft regarding a potential fix. edit: Removed Server 2016 reference. Microsoft has determined this version was not impacted.

3. monitoring Feb 07, 2025, 09:42 PM UTC

   Microsoft has conducted a thorough analysis of the problem reported to them by HYPR with the latest Cumulative Updates for Windows Server. They have determined that there was an issue introduced that causes problems for certain types of Authentication Certificates. Microsoft has provided the below information which will allow you to consume the Cumulative update while 'turning off' the specific single update responsible for this error, allowing Cert auth to work properly until they release a complete patch/fix for this issue. Info provided to us by Microsoft below: Problem Statement ================= After Applying the January 14, 2025, Cumulative Update for Windows Server 2022, or Windows Server 2019 on Domain Controllers January 14, 2025—KB5049983 (OS Build 20348.3091) - Microsoft Support https://support.microsoft.com/en-us/topic/january-14-2025-kb5049983-os-build-20348-3091-789bf923-7777-419d-9c3a-23f7c814930f January 14, 2025—KB5050008 (OS Build 17763.6775) - Microsoft Support https://support.microsoft.com/en-us/topic/january-14-2025-kb5050008-os-build-17763-6775-9a174725-a7ea-4e37-a6f8-e86f7c4d3f31 Windows Server Domain Controllers may fail to map a Client Certificate offered for Windows Logon if the Certificate Subject is "Empty". This happens even though the Certificate contains other properties as documented by Microsoft. Certificate Requirements and Enumeration | Microsoft Learn https://learn.microsoft.com/en-us/windows/security/identity-protection/smart-cards/smart-card-certificate-requirements-and-enumeration Root Cause ========== The root cause is determined to be defect included in the January 14, 2025 update for Windows Server 2022 and Windows Server 2019 that is checking the Certificate for the Subject information to be not blank. The failure return prevents the Domain Controller from finding a mapping for the Certificate within the Active Directory. Remediation/Recommendation ========================= To provide immediate temporary relief without uninstalling the January 14, 2025 Cumulative Update, Microsoft has published the Known Issue Rollback (KIR) Package for the respective Operating Systems for each Active Directory Services Domain Controller using the Microsoft documentation. Use Group Policy to deploy a Known Issue Rollback - Windows Client | Microsoft Learn https://learn.microsoft.com/en-us/troubleshoot/windows-client/group-policy/use-group-policy-to-deploy-known-issue-rollback Apply KIR to a single device using Group Policy. To use Group Policy to apply a KIR to a single device, follow these steps: 1.Download the KIR policy definition MSI file to the Domain Controller. Important: Make sure that the operating system that is listed in the .msi file name matches the operating system of the device that you want to update. Windows Server 2022 https://download.microsoft.com/download/f3c22ae2-4a00-4954-aa98-fe558e85dbc8/Windows%20Server%202022%20KB5044281%20250131_090543%20Feature%20Preview.msi Windows Server 2019 https://download.microsoft.com/download/7648edb5-d483-4ea4-9c10-69a6d58fb4bc/Windows%2010%201809%20and%20Windows%20Server%202019%20KB5044277%20250131_11501%20Feature%20Preview.msi 2.Run the .msi file on the Domain Controller. This action installs the KIR policy definition in the Administrative Template. 3.Open the Local Group Policy Editor. To do this, select Start, and then enter gpedit.msc. 4.Select Local Computer Policy > Computer Configuration > Administrative Templates > KB ####### Issue XXX Rollback > Windows 10, version YYMM. Note: In this step, ####### is the KB article number of the update that caused the problem. XXX is the issue number, and YYMM is the Windows 10 version number. 5.Right-click the policy, and then select Edit > Disabled > OK. 6.Restart the Computer. Investigation ============= Microsoft has determined the root cause of the incident. Microsoft has provided mitigations for immediate temporary relief without uninstalling the cumulative security update that has been verified by Microsoft and HYPR. Microsoft will continue to investigate a permanent solution for the incident in a future update. Additional Information / Discussion =================================== Use Group Policy to deploy a Known Issue Rollback - Windows Client | Microsoft Learn https://learn.microsoft.com/en-us/troubleshoot/windows-client/group-policy/use-group-policy-to-deploy-known-issue-rollback

4. resolved Feb 13, 2025, 02:57 PM UTC

   Resolution Microsoft has identified this problem as a bug introduced in the January 2025 Windows Update, and has fixed the problem in the February 2025 Windows Update. Windows Server 2019 February 11, 2025 — KB5052000 (OS Build 17763.6893) https://support.microsoft.com/en-us/topic/february-11-2025-kb5052000-os-build-17763-6893-2197b079-9a41-4e07-95c5-9ebce5fe20ec Windows Server 2022 February 11, 2025 — KB5051979 (OS Build 20348.3207) https://support.microsoft.com/en-gb/topic/february-11-2025-kb5051979-os-build-20348-3207-890f2739-1188-4367-bf10-4377a72db8ec These updates were published by Microsoft on February 11, 2025 (“patch Tuesday”), and will be deployed on servers configured to automatically install Windows Updates. If automatic updates are not enabled, customers can manually force the server to install the latest Windows Update via the GUI. (It can probably also be done via Group Policy, Intune, PowerShell script, etc. – these methods are left as an exercise for the reader.) Special considerations for Windows Server VM’s running in Microsoft Azure Windows Server running in an Azure VM gets different updates compared to Windows Server running on-prem or with a different provider (e.g. AWS). Windows Server on Azure gets a standard update once every quarter, and then two monthly hotpatch updates that don't require a reboot. So they only reboot once per quarter, rather than every month. The problem is that the February 2025 update on Azure is of the hotpatch variety, and it doesn't include a fix for the certificate authentication problem. Running Windows Update, either automatically or manually, will not fix the certificate problem. Microsoft has confirmed that a “standard” cumulative update package can be installed on Azure VM’s, and it won’t disrupt future hotpatch updates. Unfortunately, the standard package has to be downloaded from the Microsoft Update Catalog web site. The process isn’t too painful, but it’s not as simple as clicking one button. Windows Server 2019 Go to this Windows Update Catalog page: https://www.catalog.update.microsoft.com/Search.aspx?q=KB5052000 Click the Download button for “2025-02 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5052000)”. A secondary window will pop up. Click on the link to download the update package file: windows10.0-kb5052000-x64_4d5c653ed24d769894ed1a2855d1c59fa70135af.msu Open the downloaded MSU file, either from the browser, or using Windows Explorer. This will start the Windows Update Standalone Installer utility. When prompted, confirm that you want to install the update. Like all Windows Update processes, it may take a long time, and the progress bar may be misleading! When the update has finished installing, reboot the server. Windows Server 2022 Go to this Windows Update Catalog page: https://www.catalog.update.microsoft.com/Search.aspx?q=KB5051979 Click the Download button for “2025-02 Cumulative Update for Microsoft server operating system, version 22H2 for x64-based Systems (KB5051979)” or “2025-02 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5051979)” The updates are identical. It doesn’t matter which one you choose. A secondary window will pop up. Click on the link to download the update package file: windows10.0-kb5051979-x64_8b40fef9cafae506c09275c96e3aa883a9e3ae39.msu Open the downloaded MSU file, either from the browser, or using Windows Explorer. This will start the Windows Update Standalone Installer utility. When prompted, confirm that you want to install the update. Like all Windows Update processes, it may take a long time, and the progress bar may be misleading! When the update has finished installing, reboot the server.

Read the full incident report →