Ping Identity incident
PingOne directory service experience high un-caught exceptions
Minor Vendor's status page →
Resolved after 1 hour 17 minutes, affecting PingID Server, on May 28, 2026.
PingOne directory service is now operational in both EU regions (Active/Active)
Affected components
PingID Server
Update timeline
- investigating May 28, 2026, 10:48 AM UTC
PingOne directory service experience high number of uncaught exceptions. We are investigating the issue
- 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
- monitoring May 28, 2026, 11:05 AM UTC
Traffic failover completed in the other eu region; Restarting directory service in the failed eu region.
- monitoring May 28, 2026, 11:43 AM UTC
PingOne directory service is now operational in both EU regions (Active/Active)
- resolved May 28, 2026, 12:07 PM UTC
This incident has been resolved.
Your product runs on more than Ping Identity
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services