Live / Jamf / Incident
Jamf: Database Issues
Jamf · jamf.comMinor incidentResolved2026-10-01 07:17 UTC
Public — what happened
Summary
Jamf reported a minor incident it labeled as database issues, beginning at 06:10 UTC on October 1, 2026; it did not say which services or customers were affected. The company said it had pinpointed the problem by 06:14 UTC but did not describe a cause. Jamf reported putting a fix in place at 06:48 UTC and watching the results, and the incident was marked resolved at 07:17.
Timeline
- Started — 2026-10-01 06:10 UTC
- Investigating — 2026-10-01 06:10 UTC
- Identified — 2026-10-01 06:14 UTC
- Monitoring — 2026-10-01 06:48 UTC (2 updates)
- Resolved — 2026-10-01 07:17 UTC · 1h 07m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Jamf against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Jamf: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Jamf report →
More from Jamf
Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.