Operational Ping Identity status
pingidentity.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
Ping Identity looks fine itself, but Amazon Web Services, a provider it may run on (inferred), reports major outage. Watch for knock-on effects.
confidence: low Vendor: operational · users: normal · routing: no data · upstream providers: major.
- Vendor status page Operational · 2 open incidents
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) Amazon Web Services: Major outage
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: PingOne Admin Console, Administration API, Directory API
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 3 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “PingOne - US geography - Admin Audit Services”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
- Amazon Web Services reports an issue. Ping Identity may depend on it (inferred from public sources). Coincidence, not causation. evidence confidence: low
What we don't know: what is happening inside Ping Identity's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.
Coincidence, not causation: signals that overlap in time are shown side by side, not as proof of cause.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data · upstream providers: major. Vendor status and outside signals roughly agree.
Who depends on whom
Ping Identity may run on Amazon Web Services (inferred). We don't map other services that depend on Ping Identity. Dependency chains are where single points of failure hide.
Identity & trust lens
When Ping Identity has trouble, people see failed logins, MFA prompts that don't arrive and sessions that drop. That's when phishing pages and “verify your account” texts show up. Only sign in through the official app or site, and don't re-enter credentials from a link someone sends you.
For users
Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Ping Identity or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Ping Identity. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
PingOne - US geography - Admin Audit Services
minor resolved · started · resolved
3 updates
- investigating
Ping Identity is aware of an issue impacting PingOne Audit logs in the US geography. We are currently investigating. We will provide the next update in approximately 15 minutes, or sooner as information becomes available. 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.
- monitoring
A fix has been implemented and we are monitoring to confirm recovery. We will provide the next update in approximately 30 minutes or upon confirmation of resolution. 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.
- resolved
This incident has been resolved. If you continue to experience issues that may be related to this event, please contact Ping Identity Support at https://support.pingidentity.com.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.