Live / Jamf / Incident
Jamf: On-Device Content Filtering test page is currently unavailable
Jamf · jamf.comMinor incidentResolved2026-10-21 20:16 UTC
Public — what happened
Summary
Jamf said a test web page used to check its On-Device Content Filtering feature became unavailable, and that the problem affected only that page and not the filtering feature itself. The company reported at 08:59 UTC on October 21, 2026 that it had identified the issue and was working on a fix. A later update said filtering was working, though users might notice a slight dip in experience while engineers continued toward full restoration. Jamf marked the incident resolved at 20:16 UTC the same day.
Affected
Threat Defense
Timeline
- Started — 2026-10-21 08:59 UTC
- Identified — 2026-10-21 08:59 UTC (2 updates)
- Resolved — 2026-10-21 20:16 UTC · 11h 16m 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 44, 2026, our weekly internet health report.