WatchGuard Outage History

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.

The team has identified the cause of the delay and is actively working to resolve the issue. Unfortunately, a gap in our monitoring has resulted in incidents for some accounts being lost over the last few days. The team will be working to recover this data once the delay has been resolved. We apologize for the impact this event has caused. We'll post our next update at 21:00 UTC if not sooner.

We are continuing to actively work on resolving the incident persistence delays. We’ll post our next update at April 22, 03:00 UTC, if not sooner. Thanks for your patience.

A fix has been implemented and the delays have been resolved. The service is operating normally at this time, and we are actively monitoring to ensure system stability. Our teams continue to investigate the potential recovery of any data that may have been lost over the last few days. We will post our next update on April 22 at 16:00 UTC, if not sooner. Thank you for your continued patience and understanding.

We are seeing a recurrence of delays in incident persistence, currently around 10 hours. To help stabilize the system, Botnet Incidents are temporarily not being consumed by ThreatSync. Our teams are monitoring closely and working on a long-term solution, while also investigating the recovery of any data that may have been affected. We'll post our next update on April 22 at 20:00 UTC, if not sooner. Thanks for your patience.

We are still working hard to resolve delays in incident persistence. As a load-control measure, Botnet incidents have been fully filtered out. Our teams continue to monitor the system closely and are working on implementing a long-term fix. We will work to recover any data that may have been affected once the delays have been fully resolved. We'll post our next update on April 23 at 02:00 UTC, if not sooner. Thanks for your patience.

The delays in incident persistence have been resolved. Our teams are continuing to closely monitor system stability and are working toward a long-term fix to prevent recurrence. We will continue to investigate the recovery of any data that may have been affected. We'll post our next update on April 23 at 08:00 UTC, if not sooner. Thanks for your patience and understanding.

Our teams are continuing to actively work on data recovery efforts related to this incident. System stability remains under close monitoring, and we are focused on safely restoring any data that may be affected. We’ll provide our next update at 20:00 UTC if not sooner.

Our teams are actively working on implementing a permanent fix and continue to closely monitor the system. There are no delays at this time. We will continue to investigate the recovery of any data that may have been affected once the permanent fix has been deployed. We'll post our next update on April 24 at 02:00 UTC, if not sooner. Thanks for your patience.

A permanent fix has been implemented. Our teams will continue to closely monitor the system. We will continue to investigate the recovery of any data that may have been affected. We'll post our next update on April 24 at 08:00 UTC, if not sooner. Thanks for your patience.

We continue to investigate the data recovery process while all systems are operating normally. There is no impact to current service availability. Our next update will be shared on April 24 at 20:00 UTC, or earlier if appropriate. Thank you for your continued patience

We continue to assess the data recovery process. All systems are operating normally with no impact on service availability. The next update will be shared on April 27 at 19:00 UTC, or earlier if warranted. Thank you for your continued patience.

We continue to monitor and assess the data recovery process. All systems remain fully operational, with no impact to service availability. The next update will be provided on April 27 at 23:00 UTC, or sooner if there are any significant developments. Thank you for your continued patience.

We continue to closely monitor the situation. All systems are operating normally, and there has been no impact to service availability at this time. Our next update will be shared on April 28 at 05:00 UTC, or earlier if any notable changes occur. Thank you for your continued understanding and support

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 are currently experiencing performance issues affecting DNSWatch dashboards. Users may be experiencing slow loading reports and dashboard tiles. In some cases, timeouts may occur. 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 60 minutes, if not sooner.

We are still working hard to resolve this event. Please check back at April 17, 01:00 UTC for updates. Thanks for your patience.

We are still working hard to resolve this event. Please check back at April 17, 03:00 for updates. Thanks for your patience.

We are still working hard to resolve this event. Please check back at April 17, 07:00 UTC for updates. Thanks for your patience.

We are still working hard to resolve this event. Please check back at April 17, 13:00 UTC for updates. Thanks for your patience.

We are still working hard to resolve this event. Please check back at April 17, 19:00 UTC for updates. Thanks for your patience

We are still working hard to resolve this event. Please check back at April 18, 01:00 UTC for updates. Thanks for your patience.

We are still working hard to resolve this event. We have scaled up our infrastructure to improve performance and are continuing to make further optimizations. Please check back at April 18, 07:00 UTC for updates. Thanks for your patience.

We are still working to resolve this event. The team is currently deploying an optimization aimed at addressing the issue. We will share another update within the next two hours or sooner.

We have detected and addressed an infrastructure issue that caused delayed information of 5 hours in our Visibility Reports service. Systems are now recovering. We apologize for the impact this event has caused. We'll post our next update in 1 hour, if not sooner.

Our systems continue returning to normal. Unfortunately, the service will need few hours to completely catch up with the pending data. We're monitoring to ensure system stability and will post our next update within 1 hour.

The information delays in our Visibility Reporting service are continuing to decrease as the system returns to normal. We're monitoring to ensure stability and will post our next update within 2 hours.

We are still working hard to resolve the delays in our Visibility Reporting service. We'll post our next update by 21:15 UTC. Thank you for your patience.

We are continuing to work on resolving the remaining delays in our Visibility Reporting service. Our team is actively monitoring progress and ensuring stability. We'll post our next update by 00:15 UTC. Thank you for your continued patience.

We continue to make steady progress in reducing the remaining delays in our Visibility Reporting service. While the system is stable and processing data as expected, a queue of pending data remains, and we estimate it may take several additional hours for all delayed information to be fully processed. Our team is actively monitoring the recovery to ensure continued stability. We’ll provide our next update by April 16, 08:30 UTC.

The systems are still recovering and the overall delays in our Visibility Reporting service have improved, but they are still present, and around 2 hours of max delay. While the system is stable and processing data as expected, we estimate it may take several additional hours to completely catch-up. Our team is actively monitoring the recovery to ensure continued stability. We’ll provide our next update in the next 6 hours or earlier.

Recovery has slowed due to today’s peak traffic, but all systems are stable and actively processing data. As demand decreases, we expect the recovery pace to improve. It may take several more hours to fully process all pending data. Our team is closely monitoring the situation to ensure ongoing stability. We’ll share our next update within 6 hours, or sooner if anything changes.

We’ve added additional resources to support recovery efforts. The system remains stable and is actively working through the remaining backlog. While delays continue to improve, it will still take several more hours for the Visibility Reporting service to catch up on pending data. Our team continues to closely monitor progress to ensure stability. We’ll provide our next update by April 17th, 07:00 UTC. Thank you for your continued patience.

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.

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

We are still working hard to resolve the issue. We will post our next update within two hours.

We are still working hard to resolve the issue. We will post our next update within three hours.

We have identified the issue and a fix is being implemented. The issue is caused by a recent change in our app service that handles redirection of SAML SSO Reference URLs. We'll post our next update in 30 minutes, if not sooner.

Our team is working hard on the activation issues and have identified the issue. Some customers are getting a message of unexpected error when they try to activate products.

We are currently experiencing a service degradation affecting WatchGuard Cloud Dashboards. The root cause has been identified, and our teams are actively working on restoring normal functionality. We apologize for the impact and will provide an update in 60 minutes, if not sooner.

We are continuing to work on the service degradation affecting WatchGuard Cloud Dashboards. As part of our mitigation efforts, we have confirmed that the issue involves one of our third-party service dependencies and we apologize for the impact this event has caused. We'll post our next update in 60 minutes, if not sooner.

We are continuing to investigate the service degradation affecting WatchGuard Cloud Dashboards. The issue is related to one of our third-party service dependencies, and our teams are closely monitoring the situation. We'll post our next update in 60 minutes, if not sooner.

We are still working hard to address the service degradation impacting WatchGuard Cloud Dashboards. The issue is associated with a third-party service dependency, and our teams continue to monitor the situation closely. We'll post our next update in 2 hours, if not sooner.

We are still working hard to resolve the event, and this only affects the WatchGuard Endpoint Security Dashboard. The issue is associated with a third-party service dependency, and our teams continue to monitor the situation closely. We'll post our next update in 60 minutes, if not sooner.

We continue to work on resolving the event affecting the WatchGuard Endpoint Security Dashboard. Our teams are closely monitoring the situation, and the issue involves a third-party service dependency. We'll post our next update in 60 minutes, if not sooner.

We continue to work on resolving the event affecting the WatchGuard Endpoint Security Dashboard. Some customers may see the service working as expected, though full functionality has not yet been restored. The third-party service dependency is in the process of recovery, and our teams continue to monitor the situation closely. We’ll provide another update in 60 minutes, if not sooner. Thanks for your patience.

We are continuing efforts to resolve the event impacting the WatchGuard Endpoint Security Dashboard. While some customers may experience the service functioning normally, full functionality has not yet been restored. The third-party service dependency is currently recovering, and our teams are closely monitoring the situation. We apologize for the impact this event has caused. We’ll post our next update in 60 minutes, if not sooner. Thank you for your continued patience.

We are working on alerts on token activation 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 60 minutes, if not sooner.