Live / Jamf / Incident
Jamf: Content Filtering Not Working
Jamf · jamf.comMajor incidentResolved2026-09-10 13:18 UTC
Public — what happened
Summary
Jamf reported a major problem with its content filtering feature beginning at 13:18 UTC on September 10, 2026, affecting some customers in its AP East1, AP Northeast1, AP Northeast2 and AP Southeast1 regions. According to the company, websites that should have been blocked might have been reachable instead. Jamf said it was still looking into the issue and had not named a cause, and that customers did not need to do anything. The incident is listed with an end time of 13:50 the same day, though its last posted status was still investigating.
Timeline
- Started — 2026-09-10 13:18 UTC
- Resolved — 2026-09-10 13:50 UTC · 33 min 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 38, 2026, our weekly internet health report.