Live / Huntress / Incident
Huntress: Signal generation and SOC response delay
Huntress · huntress.comMajor incidentResolved2026-10-01 09:05 UTC
Public — what happened
Summary
Huntress reported a major incident beginning at 05:02 UTC on 2026-10-01 in which security signals were being generated late, slowing the response times of its security operations center (SOC). The company said at 05:35 UTC that it had found the problem and was working on a fix, though it did not describe the cause publicly. By 05:40 UTC it said the fix was in place and signals and detections were recovering, while SOC responses were still running behind. Huntress kept watching the situation and marked the incident resolved at 09:05.
Timeline
- Started — 2026-10-01 05:02 UTC
- Investigating — 2026-10-01 05:02 UTC
- Identified — 2026-10-01 05:35 UTC
- Monitoring — 2026-10-01 05:40 UTC (3 updates)
- Resolved — 2026-10-01 09:05 UTC · 4h 03m 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 Huntress 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 Huntress: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Huntress report →
More from Huntress
Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.