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

Admin Portal Latency due to Cloudflare issues

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

Official source (opens in a new tab)
Vendor start
Aug 21, 2025, 19:16 UTC
Vendor's clock
Resolved
Aug 21, 2025, 20:35 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
1 h 19 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

  • JumpCloud reports degraded: "Admin Portal Latency due to Cloudflare issues".[E1, E2]
  • The vendor marked it resolved at 2025-08-21 20:35 UTC.[E3, E7]

Affected products and regions

  • Components: Cloudflare CDN/Cache.[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: 2025-08-21 20:35 UTC · summary s1, evidence 9381223a1ca5bafa

Evidence (7)
  1. E1JumpCloud reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Admin Portal Latency due to Cloudflare issues". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2025-08-21 19:16 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Cloudflare CDN/Cache. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2025-08-21 20:35 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Cloudflare CDN/Cache

The vendor's feed gives no region for this incident. It is not assumed to be global.

Potential relevance

JumpCloud 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. Aug 21, 2025, 19:16 UTCVendor-reported startVendor time
  2. Aug 21, 2025, 20:35 UTCVendor-reported resolutionVendor time

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