Skip to content

Outage tracker

Ping Identity: the full evidence record

The last 24 hours in detail, 15 days of measured availability, a 12-month summary, our own incident log, Ping Identity's declared record, and how the two compare.

← Back to Ping Identity's live status

We started measuring Ping Identity on August 22, 2026, which is 15 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Ping Identity's own status page declared. Below it, any public chatter we saw about Ping Identity and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Ping Identity's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Unverified user reportsNo reports about Ping Identity in the last 24 hours, which is not evidence that nothing is wrong.
Ping Identity's status page
  1. PingOne Advanced Services - US East / US West - Logging Systems Degradation: minor incident, from 02:45 UTC to 06:00 UTC.

Each probe cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused probe is not an outage. Report bars count unverified reports, not people we verified; they never change our reading. The status-page lane is Ping Identity's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Ping Identity next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

  • Confirmation probe03:09 UTC, Europe: a new incident on their status page prompted an extra probe. Result: Ping Identity answered normally.
  • Confirmation probe03:08 UTC, Australia: a new incident on their status page prompted an extra probe. Result: Ping Identity answered normally.
  • Confirmation probe03:07 UTC, US-West: a new incident on their status page prompted an extra probe. Result: Ping Identity answered normally.
  • Confirmation probe03:07 UTC, UK: a new incident on their status page prompted an extra probe. Result: Ping Identity answered normally.
  • Confirmation probe03:07 UTC, South America: a new incident on their status page prompted an extra probe. Result: Ping Identity answered normally.

Availability by region

Availability is measured probes that succeeded, divided by every probe we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionAvailabilityProbes recorded
US-East100.00%619
US-West100.00%617
Europe100.00%613
Asia-Pacific100.00%599
US-Central100.00%59
Canada100.00%59
UK100.00%59
Southeast Asia100.00%56
Australia100.00%57
South America100.00%58

Monthly summary

Tracking Ping Identity since Aug 22, 2026. In that time our probes detected no outage. Months before that date are not tracked and carry no figure.

MonthUptimeOutagesDowntime
Oct 2025not tracked
Nov 2025not tracked
Dec 2025not tracked
Jan 2026not tracked
Feb 2026not tracked
Mar 2026not tracked
Apr 2026not tracked
May 2026not tracked
Jun 2026not tracked
Jul 2026not tracked
Aug 2026 from Aug 22, 2026100%00 min
Sep 2026100%00 min

Uptime here is the share of each month in which our probes had no outage open for Ping Identity: two consecutive failed readings from a region opens one, the first clean reading closes it. Any detected outage counts, including one seen from a single region, and an outage that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and Ping Identity's own status page contribute nothing to these figures.

Our incident log

Every outage our own probes detected for Ping Identity in the last 90 days, or since we started measuring it if that is more recent. This list is probe-only: Ping Identity's own declared incidents appear further down this page in their own attributed section, never merged with what we measured here. User reports live on the live page, in their own labeled block.

No outages detected for Ping Identity since we started measuring it on August 22, 2026. We show nothing from before that date.

Their declared record

Ping Identity's own incident history, taken from their public status feed. This is their account of what happened, not our measurement, and it never changes the incident log above or the other way around.

PingOne Advanced Services - US East / US West - Logging Systems DegradationMinor incident
Sep 4, 2026, 2:58 AM UTC to Sep 4, 2026, 5:50 AM UTC (2h 52m)resolved
their latest update (Sep 4, 2026, 5:50 AM UTC): 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.
PingOne DaVinci - Europe - DegradationMinor incident
Sep 2, 2026, 11:40 PM UTC to Sep 3, 2026, 12:45 AM UTC (1h 5m)resolved
their latest update (Sep 3, 2026, 12:45 AM UTC): 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.
PingOne Advanced Identity Cloud - US Central Region - Service DisruptionAll systems operational
Sep 1, 2026, 3:44 PM UTC to Sep 1, 2026, 5:50 PM UTC (2h 6m)resolved
their latest update (Sep 1, 2026, 5:50 PM UTC): 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.
PingID - US Region - Service DisruptionMajor outage
Aug 20, 2026, 5:41 PM UTC to Aug 20, 2026, 6:47 PM UTC (1h 6m)resolved
their latest update (Aug 20, 2026, 6:47 PM UTC): 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.
Increasing error rate in AP regionAll systems operational
Aug 16, 2026, 1:44 PM UTC to Aug 16, 2026, 2:29 PM UTC (45 min)resolved
their latest update (Aug 16, 2026, 2:29 PM UTC): This incident has been resolved.
Increased error rate in AP regionAll systems operational
Aug 16, 2026, 9:38 AM UTC to Aug 16, 2026, 10:26 AM UTC (48 min)resolved
their latest update (Aug 16, 2026, 10:26 AM UTC): This incident has been resolved.
PingOne Dock Intermittent High Response TimeMinor incident
Aug 5, 2026, 8:16 AM UTC to Aug 5, 2026, 9:17 AM UTC (1h 1m)resolved
their latest update (Aug 5, 2026, 9:17 AM UTC): 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.
Degraded performance for ForgeRock Authenticator appAll systems operational
Aug 4, 2026, 10:55 PM UTC to Aug 4, 2026, 11:00 AM UTC (0 min)resolved
their latest update (Aug 4, 2026, 11:00 AM UTC): The availability of the ForgeRock Authenticator App on Google Play Store is intermittent in some regions. The issue has been identified, and re-verification of the app on the Google Play Store is in process. This could take up to 48 hours.
PingOne EU Admin APIs Elevated Error RatesMinor incident
Jul 20, 2026, 4:30 PM UTC to Jul 20, 2026, 4:30 PM UTC (0 min)resolved
their latest update (Jul 20, 2026, 4:30 PM UTC): 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 inform…
Ping Protect US Increased LatencyMinor incident
Jul 18, 2026, 9:03 PM UTC to Jul 18, 2026, 11:08 PM UTC (2h 5m)resolved
their latest update (Jul 18, 2026, 11:08 PM UTC): This incident has been resolved.

Showing the 10 most recent of 53 incidents Ping Identity has declared in the history we hold.

These entries are Ping Identity's own declarations, taken from their public status feed, shown separately from the outages we detected ourselves. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

The scorecard

How Ping Identity's status page compared with what we measured, for every outage above that falls inside the window we have been capturing their claims.

We started recording Ping Identity's own status page on August 22, 2026, 13 days ago. This comparison covers that period only, we do not reconstruct what they said before it, and we compare only inside outages we measured ourselves.

We have not measured an outage for Ping Identity since we started recording their status page, so there is nothing to compare. That is a short measurement window, not a track record.

Ping Identity decides what their status page covers, and it may report per component while our check reaches one surface from ten regions. We state what each side measured and leave the conclusion to you. If Ping Identity believes a figure here is wrong, we publish corrections as prominently as the original.

Full detail on what a probe does and does not prove is in the methodology page.