Desktop Authenticator Enrollment Degradation

Update timeline

1. investigating Apr 30, 2026, 05:54 PM UTC

   We are currently addressing an issue impacting desktop authenticator enrollments .A subset of customers may experience intermittent delays or failures during desktop authenticator enrollment. Mitigation actions are in progress and are helping to reduce impact. Core authentication, SSO, and delivery services remain fully operational.

2. investigating Apr 30, 2026, 05:57 PM UTC

   [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [MONITORING]. Statuspage incident message [We are currently addressing an issue impacting desktop authenticator enrollments .A subset of customers may experience intermittent delays or failures during desktop authenticator enrollment. Mitigation actions are in progress and are helping to reduce impact. Core authentication, SSO, and delivery services remain fully operational.] has changed as [Mitigation actions have been implemented. The service has stabilized and recovery is underway. We will continue to monitor to ensure full resolution.]. " on alert: "Desktop Authenticator Enrollment Degradation"

3. investigating Apr 30, 2026, 06:07 PM UTC

   [Comment from Opsgenie]System noted: "Statuspage incident status [MONITORING] has changed as [RESOLVED]. Statuspage incident message [Mitigation actions have been implemented. The service has stabilized and recovery is underway. We will continue to monitor to ensure full resolution.] has changed as [The issue has been resolved. Services have returned to normal operation, and customers should no longer experience delays or failures. We apologize for any inconvenience caused and thank you for your patience.]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. " on alert: "Desktop Authenticator Enrollment Degradation"

4. resolved Apr 30, 2026, 09:06 PM UTC

   This incident has been resolved.