WatchGuard Outage History

We continue to work on reports of errors during migration to DNSWatch in WGC and have identified the issue. Failures are affecting customers who have invalid domains configured in legacy DNSWatch and are attempting to migrate. WGC DNSWatch has introduced domain validation before policies are created. Our teams are working to restore normal operations and we apologize for the impact this event has caused. We'll post our next update in approximately 8 hours, if not sooner.

We’ve identified a service degradation impacting the incident storage pipeline in the EU region. This is causing approximately 3.5 hours of delay in processing and storing incident data in ThreatSync. We’ll provide another update within the next hour or sooner if available.

Our engineering teams are actively preparing to deploy mitigation measures shortly to restore normal processing performance. We will continue to closely monitor the system to ensure stability as fixes are applied. The next update will be provided in 2 hours, or sooner if available.

We are still working hard to resolve this event. Our teams remain actively engaged in restoring normal operations, and we sincerely apologize for the impact this has caused. We'll post our next update in 2 hours, if not sooner.

A fix has been implemented to mitigate the delays, but the service is still degraded. Our teams are actively working on implementing a permanent fix. We'll post our next update in 4 hours, if not sooner.

Our engineering teams have identified the underlying cause of the incident storage delays affecting ThreatSync in the EU region. We are currently implementing mitigation steps to restore normal processing performance. Incident data continues to be processed, though delays may still be observed. We will continue to monitor the system closely to ensure stability as fixes are applied. We will provide another update in 4 HR, or sooner if available.

Mitigation measures have been applied to address the incident storage delays affecting ThreatSync in the EU region. We are currently monitoring the system closely to ensure stability and to verify that processing performance continues to improve. We will provide the next update in 4 hours, or sooner if there are any significant developments.

We continue to monitor the mitigation measures applied to the incident storage delays affecting ThreatSync in the EU region. System performance remains under observation to ensure continued stability. Our next update will be provided in 4 hours, or sooner if there are notable changes.

We're currently investigating reports and have identified an issue with a third-party service provider that is affecting the System Management console. Once we determine the impact and scale of these potential issues we'll post our next update in 1h, if not sooner.

We have identified an issue affecting Local AuthPoint users with RADIUS MSCHAPv2 authentication. Our teams are working to restore normal operations. We'll post our next update in 1h, if not sooner.

Our teams are working to restore normal operations, and we apologize for the impact this issue may have caused. We'll post our next update in 1h, if not sooner.

We are still working hard to resolve this event. We'll post our next update in 1h, if not sooner. Thanks for your patience.

Our teams are actively working to restore normal operations. We'll post our next update in 1h, if not sooner.

We have identified an infrastructure issue that is causing data delays in our Visibility Reports service current delays are around 2 hours. We have deployed mitigation actions and the system is starting its recovering process. We'll post our next update in 3 hours, if not sooner.

We have detected an infrastructure issue that is causing new data delays in our Visibility Reports service current delays are around 2 hours. The team has taken mitigation actions and the system is recovering. We'll post our next update in 3 hours, if not sooner.

Recovery is ongoing, and we’ve seen improvements in delays affecting the Visibility Reporting service, though some delay remains. The system is stable and processing data normally, and we expect it to fully catch up within the next few hours. Our team continues to actively monitor the recovery to ensure stability. We’ll provide our next update in the next 3 hours or earlier.

We continue to work on alerts while creating accounts via our public API, and have identified the issue. Our teams are working to restore normal operations, and we apologize for the impact this event has caused. We'll post our next update in 30 minutes, if not sooner.

A fix for this issue has been deployed and our systems show that the issues with new Firebox deployments using the zero-touch method are returning to normal and we're monitoring to ensure system stability. We'll post our next update in 30 minutes, if not sooner.

We continue to work on alerts on DNSWatch service and have identified the issue. Our teams are working to restore normal operations and we apologize for the impact this event has caused. We'll post our next update in 30 minutes, if not sooner.

While some DNSWatch alerts showed signs of recovery, we are still observing intermittent issues affecting the service. Our teams have identified additional factors contributing to the alerts and continue working to restore full stability. We will provide another update in 60 minutes, or sooner if available.

The issue has been identified. New activations and renewals may take several hours to become available within WatchGuard Cloud. We’ll post our next update in 3 hours, if not sooner. Thank you for your patience.

We are still experiencing delays with new product activations and renewals. The system is catching up the queue and they may take up to 20 hours to become available within WatchGuard Cloud. We’ll provide the next update in 4 hours, if not sooner. Thank you for your patience.

We are continuing to experience delays with new activations and renewals. The queue is being processed and availability within WatchGuard Cloud may take up to 16 hours. We’ll provide the next update in 4 hours, if not sooner. Thank you for your patience.

We are still experiencing delays with new product activations and renewals. The backlog queue continues to be processed, and availability within WatchGuard Cloud may still take several hours. Our teams remain engaged and are monitoring progress closely while processing continues toward normal availability. We apologize for the inconvenience and appreciate your patience. We’ll provide the next update at 16:30 UTC, if not sooner

We are currently investigating reports of users experiencing issues when attempting to sign in to their WatchGuard accounts through the SAML SSO login flow. As a workaround, users can log in using their WatchGuard credentials until the issue is resolved. We'll post our next update in 1h, if not sooner.

We continue to work on the issue affecting logins through the SAML SSO login flow. We'll post our next update in 1h, if not sooner. Thanks for your patience.

Our teams have identified the issue and continue working to restore normal operations. We apologize for the inconveniences and any impact this may have had on you or your customers. We'll post our next update in 1h, if not sooner.

We are currently experiencing delays in incident generation in ThreatSync in the EMEA region. Our teams are working to restore normal operations and we apologize for the impact this event has caused. We'll post our next update in 1 hour, if not sooner.

A fix has been implemented and incident generation delays are beginning to decrease. Our teams are actively monitoring to ensure full recovery. We'll post our next update in 1 hour, if not sooner.

We have identified the issue and are working towards resolving it. We will post our next update within 30 minutes.

We are still working to restore normal operations, and will post our next update within 30 minutes.

We have identified an issue affecting Firecloud Management Reports that resulted in a data gap in the Asia Pacific region. This gap includes data from 3/20/2026 through 3/23/2026. Our teams are actively working to restore normal reporting operations. We apologize for any inconvenience this may cause and appreciate your patience. We will provide an update within 3 hours, or sooner if new information becomes available.

We have identified an issue affecting Firecloud Management Reports that resulted in a data gap of approximately three hours. Our teams are actively working to restore normal reporting operations. We apologize for any inconvenience this may cause and appreciate your patience. We will provide an update within 3 hours, or sooner if new information becomes available.

We continue to work on alerts on AuthPoint Authentication service and have identified the issue. Our teams are working to restore normal operations and we apologize for the impact this event has caused. We'll post our next update in 30 minutes, if not sooner.

We have identified the issue and are working to resolve it. We will post out next update within three hours.