- Level
- confirmed
- Worst impact
- Degraded
- Regions
- eu
What to do
Check whether you use Ping Identity in eu. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-07-20 16:30 UTC and 2026-07-20 16:30 UTC may need a replay.Subscribe to Ping Identity's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=ping-identity works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Ping Identity 1
- resolved
Between 14:20 to 14:40 UTC, a subset of customers in the PingOne EU datacenter may have experienced elevated error rates when calling administrative endpoints. We saw no impact to end-user workflows. Ping Identity Engineers are investigating the root-cause. For the latest information regarding this event, please monitor the Ping Identity Status Page: https://status.pingidentity.com. If you are experiencing an issue not covered by these updates or require assistance, please contact Ping Identity Support at https://support.pingidentity.com.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-19297a2c36
Is Ping Identity still down?
No, this incident was resolved 2026-07-20 16:30 UTC. For Ping Identity's live state, see https://down.guide/ping-identity.
How long did it last?
0m, from 2026-07-20 16:30 UTC to 2026-07-20 16:30 UTC, by the times Ping Identity posted.
What was affected?
Ping Identity named in eu.
What caused it?
Ping Identity hasn't published a root cause. If it does, it shows here.
Where does this come from?
Ping Identity's official status page, https://status.pingidentity.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.