Skip to content
Back to JumpCloudIncident Postmortem
JumpCloud logo

JumpCloud

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

JumpCloud: vendor-reported minor incident on September 25 (tracked 1h 30m)

Sep 25, 06:30 PM → Sep 25, 08:00 PM · 1h 30m · medium

JumpCloud reported a minor-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 1h 30m, from Fri, 25 Sep 2026 18:30:03 GMT to Fri, 25 Sep 2026 20:00:08 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
1h 30m
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The vendor's own status page is the only source PulseWatch has for it.

Incident timeline

  1. Sep 25, 06:30 PM

    The vendor reported a minor-impact incident on its own status page; PulseWatch began tracking it

  2. Sep 25, 06:30 PM

    Status updated: possible issue

  3. Sep 25, 08:00 PM

    PulseWatch closed the incident

Official updates

  1. Sep 25, 06:30 PM

    JumpCloud reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: fallback