Looking for an update now? Check the current status, or follow WatchGuard Technologies for future changes.
75.9%of 58 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
82.8%
29
5
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 24Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
September 2026
2026-09-08 - AMER - Mexico/Central FireCloud PoP connection issue
Authentication:::AMERHealth and Connectivity:::AMER
monitoring
All FireCloud services in Mexico/Central Point of Presence (PoP) are operational, and there are no reported connectivity issues.
Customers experiencing authentication or connectivity issues to the Mexico/Central PoP are encouraged to contact WatchGuard Support for assistance.
Our engineering team continues to monitor the services in the region to ensure long-term stability.
monitoring
FireCloud services in Mexico/Central Point of Presence (PoP) region are operating normally after the infrastructure updates deployed earlier today. Our engineering team continues to monitor the services in the region to ensure long-term stability.
We will provide another update within the next 24 hours. We apologize for any impact this may have caused your customers. This issue affected the Mexico/Central PoP only.
monitoring
WatchGuard deployed infrastructure updates to the Mexico/Central Point of Presence (PoP). Our engineering team is monitoring and will continue to investigate the issue. We will provide another update within the next 4 hours as more information becomes available. We apologize for any impact this may have caused your customers.
investigating
We continue to work on connectivity issues the Mexico/Central Point of Presence (PoP). Infrastructure updates are being deployed to the affected region. The deployment will take between 15 and 30 minutes to complete. Any connected client to the affected PoP will briefly disconnect while the deployment takes place. We apologize for any impact this may be causing to customers. We'll post our next update in 60 minutes, if not sooner.
investigating
Some customers are experiencing connectivity issues affecting the Mexico/Central Point of Presence (PoP). Our engineering team is actively investigating the issue. We will provide another update within the next 60 minutes as more information becomes available.
We apologize for any impact this may be causing to customers. This issue is affecting connectivity through the Mexico/Central PoP only."
2026-09-04 - AMER - Mexico/Central FireCloud PoP connection issue
Authentication:::AMERHealth and Connectivity:::AMER
monitoring
WatchGuard deployed new infrastructure to increase capacity for users experiencing connectivity issues affecting the Mexico/Central Point of Presence (PoP) related to the handling of policies. Services our currently restored. Our engineering team continues monitoring and investigating the issue. We will provide another update within the next 4 hours as more information becomes available. We apologize for any impact this may have caused your customers. This issue was affecting connectivity t...
investigating
We continue to work on connectivity issues and policy handling issues affecting the Mexico/Central Point of Presence (PoP). Infrastructure updates are being deployed to the affected region.
We apologize for any impact this may be causing to customers. We'll post our next update in 60 minutes, if not sooner.
investigating
We are continuing to investigate this issue.
investigating
We continue to work on connectivity issues affecting the Mexico/Central Point of Presence (PoP). Infrastructure updates to the policy handling service will start at 19:00 UTC time and will take approximately 15 to 30 minutes to complete. FireCloud clients connected to the affected PoP region will disconnect and reconnect momentarily while the changes are being deployed.
We'll post our next update in 60 minutes, if not sooner.
investigating
We continue to work on the connectivity and policy handling issues affecting the Mexico/Central Point of Presence (PoP). The FireCloud Engineering team is preparing to make infrastructure changes to make the policy handling more reliable in this region. We'll post our next update in 60 minutes, if not sooner.
investigating
Some customers are experiencing connectivity issues affecting the Mexico/Central Point of Presence (PoP) related to the handling of policies. Our engineering team is actively investigating the issue. We will provide another update within the next hour as more information becomes available.
We apologize for any impact this may be causing to customers. This issue is affecting connectivity through the Mexico/Central PoP only.
Authentication:::AMERHealth and Connectivity:::AMER
monitoring
Connectivity and service operation at the Mexico/Central Point of Presence (PoP) have been restored. We are actively monitoring the environment to ensure continued stability while the investigation into the root cause remains ongoing. We will provide our next update within 30 minutes, or sooner if additional information becomes available
monitoring
Connectivity and service operation at the Mexico/Central Point of Presence (PoP) have been restored. We are actively monitoring the environment to ensure continued stability while the investigation into the root cause remains ongoing. We will provide our next update within 30 minutes, or sooner if additional information becomes available
investigating
Connectivity to the Mexico/Central Point of Presence (PoP) remains stable following restoration efforts. We continue to actively monitor the PoP and Engineering is still investigating the root cause. Further updates will be provided as new information becomes available in 4 hrs, if not sooner.
investigating
Connectivity issues affecting the Mexico/Central Point of Presence (PoP) are currently restored. We are actively monitoring connectivity to the PoP. Engineering continues to investigate root cause of this issue.Next update will be in 4 hrs if not sooner. Thank you for your patience.
investigating
We continue to investigate connectivity issues affecting the Mexico/Central Point of Presence (PoP).
The issue remains isolated to the Mexico/Central PoP. Our engineering team is actively working toward a resolution.
Next update will be within 4 hours, or sooner as information becomes available
investigating
We are continuing to investigate this issue.We will provide another update within the next 4 hours, or sooner if additional information becomes available.
investigating
We are continuing to investigate the connectivity issues affecting the Mexico/Central Point of Presence (PoP). Our engineering team is actively working to identify the cause and determine the appropriate resolution.
We will provide another update within the next 4 hours, or sooner if additional information becomes available.
We apologize for any continued impact this may be causing you or your customers and appreciate your patience while our team works to resolve the issue.
investigating
Some customers are experiencing connectivity issues affecting the Mexico/Central Point of Presence (PoP). Our engineering team is actively investigating the issue. We will provide another update within the next hour as more information becomes available. We apologize for any impact this may be causing you or your customers. This issue is affecting connectivity through the Mexico/Central PoP only.
August 2026
2026-08-26 - EMEA - EPDR Endpoint console under Monitoring/Endpoint Security not available
Our systems show alerts on Endpoint console 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.
identified
We continue to work on alerts on Endpoint console 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.
investigating
We are still working hard to resolve this event. Please check back at 30 minutes for updates. Thanks for your patience.
investigating
We're investigating alerts on Endpoint console service. Once we determine the impact and scale of these errors we'll post our next update in 30 minutes, if not sooner.
Legacy Incident Archive
34 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
April 2026
2026-04-29- GLOBAL - System Management console not available
minorSource not attested
Last archived state: resolved
View archived record details
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.
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.
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.
2026-04-24 - GLOBAL - AuthPoint RADIUS Authentication service degradation
minorSource not attested
Last archived state: resolved
View archived record details
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.
identified
Our teams are actively working to restore normal operations. We'll post our next update in 1h, if not sooner.
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.
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.
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.
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
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.
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.
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
2026-04-20 - EMEA - Visibility Reporting Delays
minorSource not attested
Last archived state: resolved
View archived record details
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.
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.
2026-04-17 - EMEA - Visibility Reporting Delays
minorSource not attested
Last archived state: resolved
View archived record details
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.
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.
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.
2026-04-16 - Global - DNSWatch Reporting Performance Issue
minorSource not attested
Last archived state: resolved
View archived record details
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.
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.
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.
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.
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
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.
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.
identified
We are still working hard to resolve this event. Please check back at April 17, 03:00 for updates. Thanks for your patience.
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.
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.
2026-04-15 - EMEA - Visibility Reporting Delays
minorSource not attested
Last archived state: resolved
View archived record details
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
2026-04-10 - Global - Account Creation
minorSource not attested
Last archived state: resolved
View archived record details
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.
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.
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.
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.
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.
