Skip to main content
JumpCloud

Reporting Data Delay

Degraded Lasted 8h 21m · started · JumpCloud's page

Level
confirmed
Worst impact
Degraded
Components
Reporting - US Region
Regions
us
Down Index
26of 100

What to do

  • Check whether you use JumpCloud Reporting - US Region in us. 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 8h 21m it lasted.

    Anything that failed between 2025-09-04 13:14 UTC and 2025-09-04 21:34 UTC may need a replay.
  • Subscribe to JumpCloud's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=jumpcloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from JumpCloud 5

  1. identified

    We are seeing issues with stale data on reports in JumpCloud. We have deployed the relevant fix and will continue to monitor this issue. Please note that data in reports is only affected and all other data is correct. We will update within 1 hour.

    provider

  2. identified

    We are still working on this issue. We are monitoring the reduction in stale data and will provide a further update in the next few hours.

    provider

  3. monitoring

    A fix has been implemented and we are currently monitoring the progress in updating the stale data. We will provide further updates in the next two hours.

    provider

  4. monitoring

    We are still monitoring the progress in updating the stale data. We will continue to provide regular communication. Please expect the another update within the next two hours.

    provider

  5. resolved

    This incident has been resolved. Reports data is now fully up to date.

    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-130444564f

Is JumpCloud still down?

No, this incident was resolved 2025-09-04 21:34 UTC. For JumpCloud's live state, see https://down.guide/jumpcloud.

How long did it last?

8h 21m, from 2025-09-04 13:14 UTC to 2025-09-04 21:34 UTC, by the times JumpCloud posted.

What was affected?

JumpCloud named Reporting - US Region in us.

What caused it?

JumpCloud hasn't published a root cause. If it does, it shows here.

Where does this come from?

JumpCloud's official status page, https://status.jumpcloud.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.