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 271 WatchGuard outages since June 2022. The 80 outages from the last 12 months are summarized below, with incident details, duration, and resolution 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.

Minor April 2, 2026

April 2026: 2026-04-02 - Global - Issues with new Firebox deployments using the zero-touch method

Detected Apr 2, 2026 3:01 PM EDT · Resolved Apr 2, 2026 4:21 PM EDT · Duration about 1 hour

WatchGuard experienced issues with zero-touch deployments for new Fireboxes across all regions (EMEA, APAC, and AMER), preventing automated configuration of newly deployed devices. The incident lasted 1.4 hours and was resolved after deploying a fix that restored normal zero-touch deployment functionality.

Major April 2, 2026

April 2026: 2026-04-02 - EMEA - DNSWatch resolution is not working

Detected Apr 2, 2026 4:59 AM EDT · Resolved Apr 2, 2026 8:45 AM EDT · Duration about 4 hours

WatchGuard's DNSWatch service experienced a major outage in the EMEA region for 3.8 hours, with DNS resolution not working properly. The service suffered intermittent issues even after initial signs of recovery, requiring additional troubleshooting by engineering teams. The incident was fully resolved with DNSWatch returning to normal operations across the affected region.

Minor April 1, 2026

April 2026: 2026-04-01 - GLOBAL- Issues with New Product Activations and Renewals

Detected Apr 1, 2026 2:38 PM EDT · Resolved Apr 2, 2026 2:18 PM EDT · Duration about 24 hours

WatchGuard experienced delays affecting new product activations and renewals for 23.7 hours, with services remaining operational but processing times significantly slower than normal. The issue created a backlog queue that initially required up to 20 hours for new activations and renewals to become available within WatchGuard Cloud. The company implemented fixes to address the delays and fully processed the backlog, restoring normal service operations.

Minor March 31, 2026

March 2026: 2026-03-31 - GLOBAL- Login Issues for SAML SSO Users

Detected Mar 31, 2026 3:53 AM EDT · Resolved Mar 31, 2026 7:38 AM EDT · Duration about 4 hours

WatchGuard experienced a 3.8-hour outage affecting SAML SSO login functionality across all regions, preventing users from signing into their accounts through single sign-on. Users were able to access their accounts using direct WatchGuard credentials as a workaround during the incident. The issue was resolved with a fix implementation, and WatchGuard recommended updating SAML metadata configurations in Identity Providers to prevent future disruptions.

Minor March 28, 2026

March 2026: 2026-03-28 - EMEA - Delay in ThreatSync Incident Generation

Detected Mar 28, 2026 3:16 PM EDT · Resolved Mar 28, 2026 4:28 PM EDT · Duration about 1 hour

WatchGuard's ThreatSync service experienced delays in incident generation and persistence in the EMEA region for approximately 1 hour. The incident affected the system's ability to generate security incidents in a timely manner for users in that region. The issue was resolved after engineers implemented a fix and confirmed that incident generation had returned to normal operations.