Live / Arctic Wolf / Incident
Arctic Wolf: Aurora Protect agent version 3.5 Memory Protection exclusions are not being applied
Arctic Wolf · arcticwolf.comMajor incidentResolved2026-10-07 15:53 UTC
Public — what happened
Summary
Arctic Wolf reported on October 2, 2026 at 18:34 UTC that version 3.5 of its Aurora Protect agent was ignoring some Memory Protection exclusions customers had set up, meaning applications that were meant to be exempt could be flagged or blocked. The company said it had found the cause and offered a workaround through a support article while it prepared a fix. On October 5 it released an updated 3.5 agent that devices with automatic updates would receive, though it noted some devices running an earlier 3.5 build could not upgrade automatically and later published manual upgrade steps for them. Arctic Wolf moved the incident to monitoring on October 6 and marked it resolved on October 7.
Affected
Aurora Endpoint, Aurora Endpoint
Timeline
- Started — 2026-10-02 18:34 UTC
- Identified — 2026-10-02 18:34 UTC (4 updates)
- Monitoring — 2026-10-06 19:59 UTC
- Resolved — 2026-10-07 15:53 UTC · 5 days 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 Arctic Wolf 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 Arctic Wolf: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Arctic Wolf report →
More from Arctic Wolf
Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.