Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

WatchGuard Outage History

Every past WatchGuard outage tracked by IsDown, with detection times, duration, and resolution details.

There were 276 WatchGuard outages since June 2022. The 83 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor May 4, 2026

May 2026: 2026-05-04 - EMEA- ThreatSync Incident Storage Delay

Detected May 4, 2026 9:32 AM EDT · Resolved May 4, 2026 7:25 PM EDT · Duration about 10 hours

WatchGuard's ThreatSync service experienced a degradation in the EU region's incident storage pipeline, causing approximately 3.5 hours of delay in processing and storing incident data. The issue affected incident generation and persistence components in the EMEA region for 9.9 hours total. Engineering teams deployed mitigation measures followed by a permanent fix, with the service returning to normal operations and being monitored for stability.

Minor May 1, 2026

May 2026: 2026-05-01 - EMEA- ThreatSync Incident Storage Delay

Detected May 1, 2026 2:57 PM EDT · Resolved May 1, 2026 10:41 PM EDT · Duration about 8 hours

WatchGuard's ThreatSync service experienced degradation in the incident storage pipeline affecting the EU region, causing delays in processing and persisting incident data for 7.7 hours. The incident affected both incident generation and persistence components in the EMEA region. Engineering teams identified the root cause, applied mitigation measures, and restored normal service operation.

Minor April 29, 2026

April 2026: 2026-04-29- GLOBAL - System Management console not available

Detected Apr 29, 2026 2:35 AM EDT · Resolved Apr 29, 2026 3:54 AM EDT · Duration about 1 hour

WatchGuard's System Management console was unavailable for 1.3 hours due to an issue with a third-party service provider. The incident affected global access to the management console, preventing users from managing their systems. The service was restored and returned to normal operation after the third-party issue was resolved.

Minor April 24, 2026

April 2026: 2026-04-24 - GLOBAL - AuthPoint RADIUS Authentication service degradation

Detected Apr 24, 2026 6:00 AM EDT · Resolved Apr 24, 2026 11:30 AM EDT · Duration about 6 hours

WatchGuard's AuthPoint RADIUS authentication service experienced a global degradation affecting Local AuthPoint users with RADIUS MSCHAPv2 authentication across all regions (AMER, EMEA, APAC). The incident lasted 5.5 hours before teams restored normal operations and completed monitoring to confirm full resolution.

Minor April 21, 2026

April 2026: 2026-04-21 - AMER & EMEA - ThreatSync delays in incident persistence

Detected Apr 21, 2026 8:39 AM EDT · Resolved Apr 28, 2026 1:22 AM EDT · Duration 7 days

WatchGuard's ThreatSync service experienced delays in incident persistence across AMER and EMEA regions, with some accounts experiencing gaps in event processing and lost incidents over several days. The incident lasted approximately 160 hours, during which Botnet incidents were temporarily filtered out as a load-control measure to help stabilize the system. A permanent fix was implemented and the delays were resolved, with the team conducting data recovery efforts for any affected information.

Minor April 20, 2026

April 2026: 2026-04-20 - EMEA - Visibility Reporting Delays

Detected Apr 20, 2026 12:03 PM EDT · Resolved Apr 20, 2026 3:08 PM EDT · Duration about 3 hours

An infrastructure issue caused approximately 2-hour delays in WatchGuard's Visibility Reports service, affecting Log Search, Log Manager, Dashboards and Reports in the EMEA region. The company deployed mitigation actions and scaled up infrastructure to resolve the data delays. The incident was fully resolved after 3.1 hours with all services returning to normal operation.

Minor April 17, 2026

April 2026: 2026-04-17 - EMEA - Visibility Reporting Delays

Detected Apr 17, 2026 6:08 AM EDT · Resolved Apr 17, 2026 11:11 AM EDT · Duration about 5 hours

WatchGuard experienced an infrastructure issue that caused approximately 2-hour delays in their Visibility Reports service, affecting Log Search, Log Manager, Dashboards and Reports in the EMEA region. The engineering team implemented mitigation actions and the system gradually recovered over 5.1 hours. The incident was fully resolved with all delayed data processed and normal service operations restored.

Minor April 16, 2026

April 2026: 2026-04-16 - Global - DNSWatch Reporting Performance Issue

Detected Apr 16, 2026 5:00 PM EDT · Resolved Apr 18, 2026 4:05 AM EDT · Duration 1 day

WatchGuard's DNSWatch service experienced performance issues for 35.1 hours, causing slow loading reports, dashboard tiles, and timeouts for users. The company scaled up infrastructure and deployed optimizations to address the problem. The issue was fully resolved and normal service operations were restored.

Minor April 15, 2026

April 2026: 2026-04-15 - EMEA - Visibility Reporting Delays

Detected Apr 15, 2026 9:45 AM EDT · Resolved Apr 16, 2026 8:04 PM EDT · Duration 1 day

WatchGuard experienced an infrastructure issue that caused up to 5-hour delays in their Visibility Reporting service, affecting Log Search, Log Manager, Dashboards and Reports in the EMEA region. The underlying infrastructure problem was quickly identified and addressed, but systems required over 34 hours to fully process the backlog of pending data, with recovery efforts slowed by peak traffic periods. The service returned to normal operation once all delayed data was processed and the reporting delays were eliminated.

Minor April 10, 2026

April 2026: 2026-04-10 - Global - Account Creation

Detected Apr 10, 2026 1:15 PM EDT · Resolved Apr 10, 2026 3:44 PM EDT · Duration about 2 hours

WatchGuard experienced issues with account creation through their public API, affecting Account Administration services across all regions (AMER, EMEA, and APAC). The incident lasted 2.5 hours while teams investigated, identified, and deployed a fix for the API alerts. Service was restored to normal operations and the issue was fully resolved.