Live / WatchGuard Technologies / Incident
WatchGuard Technologies: 2026-10-14 - GLOBAL - DNSWatch v1 portal is not accessible
WatchGuard Technologies · watchguard.comMinor incidentResolved2026-10-14 23:51 UTC
Public — what happened
Summary
WatchGuard Technologies reported that customers could not reach its DNSWatch v1 portal at dnswatch.watchguard.com starting at 22:02 UTC on 2026-10-14, with some people seeing HTTP 500 errors when trying to load it. The company said its teams were looking into the problem but did not share a cause in its updates. At 23:19 UTC it said the portal was returning after its engineers made a fix, and it kept watching the service before marking the incident resolved at 23:51.
Affected
Administration:::GLOBE, Dashboard:::GLOBE, Blackhole:::GLOBE, Console:::GLOBE, Content Filtering:::GLOBE, Protection:::GLOBE, Firebox Registrations:::GLOBE
Timeline
- Started — 2026-10-14 22:02 UTC
- Investigating — 2026-10-14 22:02 UTC (3 updates)
- Monitoring — 2026-10-14 23:19 UTC
- Resolved — 2026-10-14 23:51 UTC · 1h 49m 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 43, 2026, our weekly internet health report.