Ping Identity incident

Some Android users are not able to use their PingID application or custom app with PingOne MFA SDK

Minor Resolved View vendor source →

Ping Identity experienced a minor incident on June 21, 2025 affecting PingID App and PingOne MFA and 1 more component, lasting 5h 58m. The incident has been resolved; the full update timeline is below.

Started
Jun 21, 2025, 05:35 PM UTC
Resolved
Jun 21, 2025, 11:33 PM UTC
Duration
5h 58m
Detected by Pingoru
Jun 21, 2025, 05:35 PM UTC

Affected components

PingID AppPingOne MFAPingOne MFAPingOne MFA

Update timeline

  1. investigating Jun 21, 2025, 05:35 PM UTC

    We are currently investigating this issue.

  2. investigating Jun 21, 2025, 06:14 PM UTC

    PingID users are unable to perform MFA with push notifications to Android devices at this time. One Time Passcodes on Android devices continue to function. We continue to investigate.

  3. investigating Jun 21, 2025, 06:15 PM UTC

    We are continuing to investigate this issue.

  4. identified Jun 21, 2025, 06:49 PM UTC

    PingOne Multitenant MFA Android users are experiencing a global service degradation. A change in the data format of the Certificate Transparency API broke a widely used Android library that provides Certificate Transparency verification. This issue prevents Android devices from validating SSL certificates during MFA push operations. All other MFA operations such as email, OTP, and SMS remain operational. We continue to investigate the best path toward resolution.

  5. identified Jun 21, 2025, 08:01 PM UTC

    Still investigating.

  6. identified Jun 21, 2025, 09:09 PM UTC

    The service provider is working to address the issue and has provided a 2-hour ETA.

  7. identified Jun 21, 2025, 10:10 PM UTC

    The service provider is still working on resolving the issue.

  8. identified Jun 21, 2025, 10:42 PM UTC

    The service provider has deployed a fix. We are experiencing signs of recovery.

  9. resolved Jun 21, 2025, 11:33 PM UTC

    The service provider's fix appears to have resolved the issue. This incident is now closed.