WatchGuard Technologies Outage History
Uptime record, past incidents, and downtime history for WatchGuard Technologies.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| May 2026 | 75% | 12 | 3 |
| April 2026 | 23.3% | 30 | 23 |
| March 2026 | 50% | 4 | 2 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 46 Days)
Mar 28
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
May 2026
2026-05-04 - EMEA- ThreatSync Incident Storage Delay
Started: May 4, 1:32 PM
monitoring
A permanent fix has been deployed and the service is operating normally. We’re monitoring to ensure system stability. We'll post our next update in 60 minutes, if not sooner.
May 4, 10:52 PM
identified
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.
May 4, 6:54 PM
identified
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.
May 4, 4:52 PM
identified
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.
May 4, 2:50 PM
identified
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.
May 4, 1:32 PM
2026-05-01 - EMEA- ThreatSync Incident Storage Delay
Started: May 1, 6:57 PM
monitoring
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 in 3o minutes.
May 2, 2:09 AM
identified
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.
May 2, 12:30 AM
identified
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.
May 1, 8:19 PM
identified
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.
May 1, 8:00 PM
investigating
Our team has identified a degradation affecting the incident storage pipeline in the EU region. This is causing delays in processing and persisting incident data within ThreatSync. We'll post our next update in an hour, if not sooner.
May 1, 6:57 PM
April 2026
2026-04-29- GLOBAL - System Management console not available
Started: Apr 29, 6:35 AM
monitoring
We are no longer experiencing issues with the System Management console. The service is operating normally at this time, we apologize for any impact this may have had on you or your customers. We will post our next update in 30 minutes, if not sooner.
Apr 29, 7:25 AM
identified
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.
Apr 29, 6:36 AM
investigating
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.
Apr 29, 6:35 AM
2026-04-24 - GLOBAL - AuthPoint RADIUS Authentication service degradation
Started: Apr 24, 10:00 AM
monitoring
We are no longer experiencing issues on Local AuthPoint users with RADIUS MSCHAPv2 authentication and this incident is now resolved. The service is operating normally at this time, we apologize for any impact this may have had on you or your customers.
Apr 24, 2:52 PM
identified
Our teams are actively working to restore normal operations. We'll post our next update in 1h, if not sooner.
Apr 24, 1:02 PM
identified
We are still working hard to resolve this event. We'll post our next update in 1h, if not sooner. Thanks for your patience.
Apr 24, 12:01 PM
identified
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.
Apr 24, 11:02 AM
identified
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.
Apr 24, 10:00 AM
2026-04-21 - AMER & EMEA - ThreatSync delays in incident persistence
Started: Apr 21, 12:39 PM
identified
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
Apr 27, 11:03 PM
identified
We continue to monitor. 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.
Apr 27, 8:00 PM
identified
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.
Apr 24, 8:08 PM
identified
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
Apr 24, 8:49 AM
identified
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.
Apr 24, 1:51 AM
identified
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.
Apr 23, 7:56 PM
identified
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.
Apr 23, 8:03 AM
identified
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.
Apr 23, 2:22 AM
identified
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.
Apr 22, 8:03 PM
identified
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.
Apr 22, 4:03 PM
identified
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.
Apr 22, 1:13 AM
identified
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.
Apr 21, 9:08 PM
identified
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.
Apr 21, 2:55 PM
investigating
We are investigating delays in incident persistence. Once we determine the impact and scale of these we'll post our next update in 2 hours, if not sooner.
Apr 21, 12:39 PM
2026-04-20 - EMEA - Visibility Reporting Delays
Started: Apr 20, 4:03 PM
monitoring
We have scaled up our infrastructure and data delays in the Visibility Reports service have been fully resolved. Our systems show that all services are operating normally and we’re continuing to monitor to ensure system stability. We'll post our next update in 30 minutes, if not sooner.
Apr 20, 6:34 PM
identified
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.
Apr 20, 4:03 PM
2026-04-17 - EMEA - Visibility Reporting Delays
Started: Apr 17, 10:08 AM
monitoring
The Visibility Reporting service has fully recovered, and all delayed data has been processed. The system is operating normally. We will continue monitoring for the next 60 minutes to ensure stability before closing the incident. Thank you for your patience.
Apr 17, 2:02 PM
identified
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.
Apr 17, 12:58 PM
identified
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.
Apr 17, 10:08 AM
2026-04-16 - Global - DNSWatch Reporting Performance Issue
Started: Apr 16, 9:00 PM
monitoring
We have implemented a fix and are seeing DNSWatch dashboards operating normally again. Users should no longer experience slow loading times or timeouts. Our teams will continue monitoring closely, and if stability is maintained, we expect to close this incident within the next 30 minutes.
Apr 18, 7:30 AM
identified
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.
Apr 18, 7:00 AM
identified
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.
Apr 18, 1:12 AM
identified
We are still working hard to resolve this event. Please check back at April 18, 01:00 UTC for updates. Thanks for your patience.
Apr 17, 6:51 PM
identified
We are still working hard to resolve this event. Please check back at April 17, 19:00 UTC for updates. Thanks for your patience
Apr 17, 12:59 PM
identified
We are still working hard to resolve this event. Please check back at April 17, 13:00 UTC for updates. Thanks for your patience.
Apr 17, 7:02 AM
identified
We are still working hard to resolve this event. Please check back at April 17, 07:00 UTC for updates. Thanks for your patience.
Apr 17, 2:57 AM
identified
We are still working hard to resolve this event. Please check back at April 17, 03:00 for updates. Thanks for your patience.
Apr 17, 12:46 AM
identified
We are still working hard to resolve this event. Please check back at April 17, 01:00 UTC for updates. Thanks for your patience.
Apr 16, 9:59 PM
identified
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.
Apr 16, 9:00 PM
2026-04-15 - EMEA - Visibility Reporting Delays
Started: Apr 15, 1:45 PM
monitoring
The Visibility Reporting service has fully caught up, and all delayed data has now been processed. The system is operating normally. We’ll continue to monitor closely for the next 60 minutes to ensure sustained stability before closing this incident. Thank you for your patience throughout the recovery.
Apr 16, 11:00 PM
identified
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.
Apr 16, 8:14 PM
identified
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.
Apr 16, 2:26 PM
identified
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.
Apr 16, 8:34 AM
identified
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.
Apr 16, 12:07 AM
identified
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.
Apr 15, 9:16 PM
identified
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.
Apr 15, 6:04 PM
identified
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.
Apr 15, 4:06 PM
identified
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.
Apr 15, 3:01 PM
identified
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.
Apr 15, 1:45 PM
2026-04-10 - Global - Account Creation
Started: Apr 10, 5:15 PM
monitoring
Our systems show alerts while creating accounts via our public API have returned to normal in all regions. We're monitoring to ensure system stability. We'll post our next update in 30 minutes, if not sooner.
Apr 10, 7:16 PM
monitoring
The fix is still actively being deployed and we continue to monitor. We'll post our next update in 30 minutes, if not sooner.
Apr 10, 6:52 PM
monitoring
A fix is actively being deployed, and our systems are showing alerts while creating accounts via our public API are returning to normal, and we are monitoring to ensure system stability. We'll post our next update in 30 minutes, if not sooner.
Apr 10, 6:24 PM
identified
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.
Apr 10, 5:24 PM
investigating
We're investigating alerts while creating accounts via our public API. Once we determine the impact and scale of this issue, we'll post our next update in 30 minutes, if not sooner.
Apr 10, 5:15 PM
2026-04-02 - Global - Issues with new Firebox deployments using the zero-touch method
Started: Apr 2, 7:01 PM
monitoring
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.
Apr 2, 7:39 PM
identified
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.
Apr 2, 7:39 PM
investigating
We are investigating issues with Zero-touch deployments for new Fireboxes. We'll post an update within the next 30 minutes.
Apr 2, 7:01 PM
2026-04-02 - EMEA - DNSWatch resolution is not working
Started: Apr 2, 8:59 AM
monitoring
The DNSWatch service remains stable, and no new alerts have been observed since the last update. We will continue to monitor closely to ensure stability is maintained across the EMEA region. Our next update will be shared in 90 minutes, or sooner if there are any changes.
Apr 2, 11:13 AM
monitoring
Our systems show alerts on the DNSWatch service are returning to normal and we're monitoring to ensure system stability across the EMEA region. We'll post our next update in 30 minutes, if not sooner.
Apr 2, 10:45 AM
identified
While some DNSWatch alerts showed signs of recovery, we are still observing intermittent issues affecting the service. <br>
Our teams have identified additional factors contributing to the alerts and continue working to restore full stability. <br><br>
We will provide another update in 60 minutes, or sooner if available.
Apr 2, 9:41 AM
monitoring
Our systems show alerts on DNSWatch service are returning to normal and we're monitoring to ensure system stability. We'll post our next update in 30 minutes, if not sooner.
Apr 2, 9:18 AM
identified
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.
Apr 2, 9:10 AM
investigating
We're investigating alerts on DNSWatch service. Once we determine the impact and scale of these errors we'll post our next update in 30 minutes, if not sooner.
Apr 2, 8:59 AM
2026-04-01 - GLOBAL- Issues with New Product Activations and Renewals
Started: Apr 1, 10:30 PM
monitoring
Our teams are continuing to observe system performance while the remaining backlog is being processed. We will provide the next update in approximately 1 hour, or sooner if there are any significant developments. Thank you for your continued patience
Apr 2, 5:43 PM
monitoring
We have implemented changes to address the delays affecting new product activations and renewals. The backlog queue continues to be processed, and services within WatchGuard Cloud are returning to normal availability.
Our teams are actively monitoring the system to ensure stability and continued progress as the remaining queue is cleared.
We appreciate your patience and will provide another update in an hour if not sooner.
Apr 2, 4:43 PM
identified
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. <br><br>
Our teams remain engaged and are monitoring progress closely while processing continues toward normal availability. We apologize for the inconvenience and appreciate your patience.<br><br>
We’ll provide the next update at 16:30 UTC, if not sooner
Apr 2, 6:38 AM
identified
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.
Apr 2, 2:41 AM
identified
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.
Apr 1, 10:29 PM
identified
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.
Apr 1, 7:47 PM
investigating
We’re investigating delays affecting new product activations and renewals. Services remain operational, with processing times slower than expected. We'll post our next update in 1 hour, if not sooner.
Apr 1, 6:38 PM
March 2026
2026-03-31 - GLOBAL- Login Issues for SAML SSO Users
Started: Mar 31, 7:53 AM
monitoring
Our team has implemented a fix, and SAML SSO login to the Web UI is now functioning normally. We are continuing to monitor the system to ensure stability.
While most SSO integrations will continue to work without any changes. We recommend updating your WatchGuard SAML metadata configuration in your Identity Provider (IdP) to ensure uninterrupted SSO login access.
Please update the SAML metadata configuration at your end as configured during your initial SSO setup, by referring to the relevan...
Mar 31, 11:05 AM
identified
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.
Mar 31, 10:03 AM
identified
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.
Mar 31, 8:57 AM
identified
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.
Mar 31, 7:53 AM
2026-03-28 - EMEA - Delay in ThreatSync Incident Generation
Started: Mar 28, 7:16 PM
monitoring
Our systems indicate that incident generation has returned to normal and we continue to monitor to ensure system stability. We'll post our next update in 30 minutes, if not sooner.
Mar 28, 7:53 PM
identified
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.
Mar 28, 7:33 PM
identified
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.
Mar 28, 7:16 PM