Skip to content
Back to JamfIncident Postmortem
Jamf logo

Jamf

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

Jamf: vendor-reported major incident on November 4 (tracked 12h 10m)

Nov 4, 09:27 AM → Nov 4, 09:37 PM · 12h 10m · high

Jamf reported a major-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked this incident for 12h 10m, closing it on 2026-11-04T21:37:21.093Z.

Duration
12h 10m
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident and therefore cannot describe what users experienced. The incident is known from Jamf's own status page.

Incident timeline

  1. Nov 4, 09:27 AM

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

  2. Nov 4, 09:27 AM

    Status updated: possible issue

  3. Nov 4, 09:37 PM

    PulseWatch closed the incident

Official updates

  1. Nov 4, 09:27 AM

    Jamf 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: gemini-2.5-flash