Live / Huntress / Incident
Huntress: Processing delays
Huntress · huntress.comResolved2026-10-22 19:37 UTC
Public — what happened
Summary
Huntress reported an incident it called "Processing delays," which began on October 22, 2026 at 14:28 UTC. The company said it had found the problem and was working on a fix at that time, though it did not describe what was affected or who was impacted. At 16:36 UTC Huntress said a fix was in place and it was watching the results, and the incident was marked resolved at 19:37 UTC.
Affected
Management Portal (huntress.io), Incident Reports
Timeline
- Started — 2026-10-22 14:28 UTC
- Identified — 2026-10-22 14:28 UTC
- Monitoring — 2026-10-22 16:36 UTC
- Resolved — 2026-10-22 19:37 UTC · 5h 09m 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 44, 2026, our weekly internet health report.