WatchGuard incident

2026-10-14 - GLOBAL - DNSWatch v1 portal is not accessible

Minor Resolved View vendor source →

WatchGuard experienced a minor incident on October 14, 2026 affecting Administration:::GLOBE and Dashboard:::GLOBE and 1 more component, lasting 1h 49m. The incident has been resolved; the full update timeline is below.

Started
Oct 14, 2026, 10:02 PM UTC
Resolved
Oct 14, 2026, 11:51 PM UTC
Duration
1h 49m
Detected by Pingoru
Oct 14, 2026, 10:02 PM UTC

Affected components

Administration:::GLOBEDashboard:::GLOBEBlackhole:::GLOBEConsole:::GLOBEContent Filtering:::GLOBEProtection:::GLOBEFirebox Registrations:::GLOBE

Update timeline

  1. investigating Oct 14, 2026, 10:02 PM UTC

    We're investigating an issue preventing customers from accessing the DNSWatch v1 portal at dnswatch.watchguard.com. Users may encounter HTTP 500 errors when attempting to load the portal. Our teams are investigating the issue and working to identify the cause. We apologize for the inconvenience and will provide another update within 60 minutes, or sooner if additional information becomes available.

  2. investigating Oct 14, 2026, 11:03 PM UTC

    We're continuing to investigate the issue preventing customers from accessing the DNSWatch v1 portal at dnswatch.watchguard.com. Users may encounter HTTP 500 errors when attempting to load the portal. Our teams are actively investigating and working to restore normal access. We apologize for the inconvenience and will provide our next update within 2 hours, or sooner if additional information becomes available.

  3. investigating Oct 14, 2026, 11:16 PM UTC

    We are continuing to investigate this issue.

  4. monitoring Oct 14, 2026, 11:19 PM UTC

    The DNSWatch v1 portal is coming back online following remediation by our engineering team. We are monitoring the service to ensure that access is fully restored and the portal remains stable. We apologize for the inconvenience and will provide our next update within 30 minutes, or sooner if further information becomes available.

  5. resolved Oct 14, 2026, 11:51 PM UTC

    This incident is now resolved. The system is operating normally at this time.