Live / WatchGuard Technologies / Incident
WatchGuard Technologies: 2026-11-09 GLOBAL SiemFeeder service connection failures
WatchGuard Technologies · watchguard.comMajor incidentResolved2026-11-09 20:17 UTC
Public — what happened
Summary
WatchGuard Technologies said that starting at 15:53 UTC on 2026-11-09, clients of its Endpoint Security SIEM service could not connect and might see a 403 error. The company said only WatchGuard Endpoint Security customers were affected, and that Aether and Cytomic customers were not. By 17:59 UTC it said it had identified the issue and was working to restore normal operations, and the incident is now marked resolved as of 20:17 UTC.
Affected
Administration:::AMER, Administration:::EMEA, Administration:::APAC
Timeline
- Started — 2026-11-09 15:53 UTC
- Investigating — 2026-11-09 15:53 UTC (2 updates)
- Identified — 2026-11-09 17:59 UTC (2 updates)
- Resolved — 2026-11-09 20:17 UTC · 4h 23m 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 WatchGuard Technologies 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 WatchGuard Technologies: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the WatchGuard Technologies report →
More from WatchGuard Technologies
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.