Ping Identity incident

PingOne directory service experience high un-caught exceptions

Minor Resolved View vendor source →

Ping Identity experienced a minor incident on May 28, 2026 affecting PingID Server, lasting 1h 17m. The incident has been resolved; the full update timeline is below.

Started
May 28, 2026, 10:49 AM UTC
Resolved
May 28, 2026, 12:07 PM UTC
Duration
1h 17m
Detected by Pingoru
May 28, 2026, 10:49 AM UTC

Affected components

PingID Server

Update timeline

  1. investigating May 28, 2026, 10:48 AM UTC

    PingOne directory service experience high number of uncaught exceptions. We are investigating the issue

  2. identified May 28, 2026, 10:49 AM UTC

    A bot network attack was identified, and customer traffic is failed over to the other eu region

  3. monitoring May 28, 2026, 11:05 AM UTC

    Traffic failover completed in the other eu region; Restarting directory service in the failed eu region.

  4. monitoring May 28, 2026, 11:43 AM UTC

    PingOne directory service is now operational in both EU regions (Active/Active)

  5. resolved May 28, 2026, 12:07 PM UTC

    This incident has been resolved.