Vendor reports: degradedResolved · vendor status “resolved”Official status API

Intermittent issue with PingOne for Enterprise Cloud Desktop in NA (503 HTTP responses)

Reported by Ping Identity · Identity & Security · source last read 3 min ago

Vendor start
Mar 11, 2026, 15:55 UTC
Vendor's clock
Resolved
Mar 11, 2026, 19:34 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
3 h 39 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Ping Identity reports degraded: "Intermittent issue with PingOne for Enterprise Cloud Desktop in NA (503 HTTP responses)".[E1, E2]
  • The vendor marked it resolved at 2026-03-11 19:34 UTC.[E3, E7]

Affected products and regions

  • Components: PingOne Dock.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-03-11 19:34 UTC · summary s1, evidence 41914caecb0eeeac

Evidence (7)
  1. E1Ping Identity reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Intermittent issue with PingOne for Enterprise Cloud Desktop in NA (503 HTTP responses)". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-03-11 15:55 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: PingOne Dock. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-03-11 19:34 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: PingOne Dock

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Ping Identity is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Mar 11, 2026, 15:55 UTCVendor-reported startVendor time
  2. Mar 11, 2026, 19:34 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.