WatchGuard Outage History

Started Jul 24, 2026, 01:58 PM UTC· resolved Jul 24, 2026, 03:01 PM UTC

1. monitoring Jul 24, 2026, 01:58 PM UTC

   Between 11:07 UTC and 12:14 UTC, we identified and resolved an issue that impacted a subset of Firebox and DNS services in the AMER region, including Firebox Configuration, Firebox Live Status, and DNS services. The service is operating normally at this time and we are monitoring to ensure system stability. We apologize for the impact this may have had on you or your customers. Our next update will be posted in 60 minutes, if not sooner.

2. resolved Jul 24, 2026, 03:01 PM UTC

   We are no longer experiencing alerts on Firebox and DNS services and this incident is now resolved. The service is operating normally at this time.

Read the full incident report →

Started Jul 24, 2026, 01:22 PM UTC· resolved Jul 24, 2026, 02:24 PM UTC

1. monitoring Jul 24, 2026, 01:22 PM UTC

   Between 11:07 UTC and 12:14 UTC, we identified and resolved an issue that impacted a subset of AuthPoint authentication requests using password-only or password + MFA authentication. The service is operating normally at this time and we are monitoring to ensure system stability. We apologize for the impact this may have had on you or your customers, our next update will be posted in 60 minutes, if not sooner.

2. resolved Jul 24, 2026, 02:24 PM UTC

   We are no longer experiencing AuthPoint authentication services and this incident is now resolved. The service is operating normally at this time.

Read the full incident report →

Started Jul 23, 2026, 03:31 PM UTC· resolved Jul 23, 2026, 08:30 PM UTC

1. investigating Jul 23, 2026, 03:31 PM UTC

   We're investigating alerts on activations & logging into WatchGuard Cloud. Once we determine the impact and scale of this potential issue we'll post our next update in 30 minutes, if not sooner.

2. investigating Jul 23, 2026, 03:58 PM UTC

   We continue to work on alerts for activations, logins, and account creation on WatchGuard Cloud. We'll post our next update in 30 minutes, if not sooner.

3. identified Jul 23, 2026, 04:26 PM UTC

   We continue to work on alerts for activations, logins, and account creation and have identified networking issues. 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.

4. identified Jul 23, 2026, 05:25 PM UTC

   We continue to remediate the networking issues impacting activations, logins, and account creation in WatchGuard Cloud. Work remains ongoing across multiple teams as we focus on restoring service functionality. We appreciate your continued patience and will post our next update in 60 minutes, if not sooner.

5. identified Jul 23, 2026, 06:25 PM UTC

   We continue to work on remediating the networking issues impacting activations, logins, and account creation in WatchGuard Cloud. The issue was caused by problems within our third-party infrastructure provider. Our teams continue working to restore full service functionality as quickly as possible. We appreciate your continued patience and apologize for the impact this event has caused. We'll post our next update in 60 minutes, if not sooner.

6. monitoring Jul 23, 2026, 07:24 PM UTC

   We are beginning to see service recovery for activations, logins, and account creation in WatchGuard Cloud. Services are returning to normal, and we are monitoring to ensure system stability. The issue was caused by problems within our third-party infrastructure provider. We appreciate your continued patience and will post our next update in 60 minutes, if not sooner.

7. resolved Jul 23, 2026, 08:30 PM UTC

   We are no longer experiencing issues with activations, logins, and account creation in WatchGuard Cloud, and this event is now resolved. Services are operating normally at this time. The issue was caused by problems within our third-party infrastructure provider. We appreciate your continued patience and apologize again for any impact this may have had on you or your customers.

Read the full incident report →

Started Jul 23, 2026, 09:51 AM UTC· resolved Jul 23, 2026, 01:11 PM UTC

1. investigating Jul 23, 2026, 09:51 AM UTC

   We're investigating alerts on DNS Activation services. Once we determine the impact and scale of these errors we'll post our next update in 60 minutes, if not sooner.

2. investigating Jul 23, 2026, 10:59 AM UTC

   We are still working hard to resolve this event. Please check back at 30 minutes for updates. Thanks for your patience.

3. identified Jul 23, 2026, 11:47 AM UTC

   We continue to work on alerts on DNS Activation services 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.

4. monitoring Jul 23, 2026, 12:39 PM UTC

   Our systems show alerts on DNS Activation 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.

5. monitoring Jul 23, 2026, 01:10 PM UTC

   We are no longer experiencing alerts on DNS Activation service and this incident is now resolved. The service is operating normally at this time.

6. resolved Jul 23, 2026, 01:11 PM UTC

   We are no longer experiencing alerts on DNS Activation service and this incident is now resolved. The service is operating normally at this time.

Read the full incident report →

Started Jul 06, 2026, 05:12 PM UTC· resolved Jul 06, 2026, 07:00 PM UTC

1. investigating Jul 06, 2026, 05:12 PM UTC

   We're investigating errors when viewing firmware upgrade details. Once we determine the impact and scale of these errors, we'll post our next update in 30 minutes, if not sooner.

2. investigating Jul 06, 2026, 05:41 PM UTC

   We continue to investigate errors when viewing firmware upgrade details and will post our next update in 30 minutes if not sooner.

3. identified Jul 06, 2026, 06:04 PM UTC

   We continue to work on errors when viewing firmware upgrade details 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.

4. monitoring Jul 06, 2026, 06:31 PM UTC

   Our systems show errors when viewing firmware upgrade details are returning to normal and we're monitoring to ensure system stability. We'll post our next update in 30 minutes, if not sooner.

5. resolved Jul 06, 2026, 07:00 PM UTC

   We are no longer experiencing errors when viewing firmware upgrade details and this event is now resolved. The system is operating normally at this time.

Read the full incident report →

Started Jul 02, 2026, 01:12 PM UTC· resolved Jul 02, 2026, 03:12 PM UTC

1. investigating Jul 02, 2026, 01:12 PM UTC

   We're investigating alerts on ThreatSync incident service. Once we determine the impact and scale of these errors we'll post our next update in 30 minutes, if not sooner.

2. identified Jul 02, 2026, 01:23 PM UTC

   We continue to work on ThreatSync incidents 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.

3. identified Jul 02, 2026, 02:18 PM UTC

   We are still working hard to resolve this event. Please check back at 30 minutes for updates. Thanks for your patience.

4. monitoring Jul 02, 2026, 02:49 PM UTC

   Our systems show alerts on ThreatSync incidents 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.

5. resolved Jul 02, 2026, 03:12 PM UTC

   We are no longer experiencing alerts on ThreatSync incidents service and this incident is now resolved. The service is operating normally at this time.

Read the full incident report →

Started Jun 26, 2026, 10:20 AM UTC· resolved Jun 26, 2026, 11:21 AM UTC

1. investigating Jun 26, 2026, 10:20 AM UTC

   We're investigating errors in retrieving account details. Once we determine the impact and scale of these errors we'll post our next update in 30 minutes, if not sooner.

2. identified Jun 26, 2026, 10:30 AM UTC

   The team has identified the issue impacting account and operator administration in the WatchGuard Cloud console and is actively working to restore normal operations. We apologize for any inconvenience this may be causing you or your customers. We will provide the next update in 30 minutes, if not sooner.

3. monitoring Jun 26, 2026, 10:45 AM UTC

   The issue has been resolved by our team, and account and operator administration services are returning to normal operations. We are continuing to monitor the system to ensure stability. We apologize for the inconvenience and any impact this may have had on you or your customers.

4. resolved Jun 26, 2026, 11:21 AM UTC

   We are no longer experiencing errors with the account and operator administration and this incident is now resolved. Again, we apologize for any impact this may have had on you or your customers.

Read the full incident report →

Started Jun 19, 2026, 12:50 PM UTC· resolved Jun 19, 2026, 06:04 PM UTC

1. identified Jun 19, 2026, 12:50 PM UTC

   We have identified an issue affecting administration managed access in WatchGuard Cloud when some users try to enable support access. The team is already working on a fix, we will post our next update in 1 hour or earlier.

2. identified Jun 19, 2026, 01:52 PM UTC

   We continue to work on resolving the event affecting administration managed access in WatchGuard Cloud. Our team is 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.

3. identified Jun 19, 2026, 02:56 PM UTC

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

4. monitoring Jun 19, 2026, 05:35 PM UTC

   A fix has been deployed to address the issue affecting the administration of managed access in WatchGuard Cloud when trying to enable support access. We are monitoring to ensure system stability. We'll post our next update in 30 minutes if not sooner.

5. resolved Jun 19, 2026, 06:04 PM UTC

   We are no longer experiencing errors while enabling managed access in WatchGuard Cloud. This incident is now resolved. The system is operating normally at this time.

Read the full incident report →

Started Jun 10, 2026, 01:55 PM UTC· resolved Jun 11, 2026, 03:10 AM UTC

1. investigating Jun 10, 2026, 01:55 PM UTC

   We are currently investigating a service degradation affecting the WES Endpoint Console. Once we determine the impact and scale of these errors we'll post our next update in 30 minutes, if not sooner.

2. identified Jun 10, 2026, 02:21 PM UTC

   Our teams have identified the issue and implemented a fix. Services are beginning to recover, though there is currently a processing delay of approximately 2 hours. We'll post our next update in 1h if not sooner. Thank you for your patience and understanding.

3. identified Jun 10, 2026, 03:37 PM UTC

   The systems are still recovering and the overall delays is around 2 hours. 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 2 hours or earlier. We are sorry for any inconvenience this may have caused you or your customers and thank you for your patience.

4. monitoring Jun 10, 2026, 05:29 PM UTC

   The issue has been resolved and services are operating normally. However, some queues may continue to experience delays while we process the backlog generated during the incident. Our team is actively monitoring the environment and working to ensure all queued items are processed as quickly as possible. We appreciate your patience and understanding throughout this incident. We will continue to monitor the situation and provide further updates in next 2hrs.

5. monitoring Jun 10, 2026, 07:47 PM UTC

   The issue remains resolved, and services are operating normally. Signal generation is processing on time. We are currently observing some delays in Attestation processing. Our team continues to monitor the environment and backlog closely. The next update will be provided in 4 hours, or sooner if there are any significant changes. Thank you for your continued patience

6. monitoring Jun 10, 2026, 11:29 PM UTC

   Services continue to operate normally following the resolution of the incident. The backlog generated during the incident is continuing to be processed, and signal generation is occurring within expected timeframes. Some delays may still be experienced within Attestation processing. Our team continues to actively monitor the environment and backlog recovery to ensure all queued items are processed successfully. Next update: 4 hours from now, or sooner if significant changes occur.

7. resolved Jun 11, 2026, 03:10 AM UTC

   Issue has been fully resolved, and all services are operating normally. The backlog generated during the incident has been successfully processed, and delayed queue items have caught up. Signal generation and Attestation processing are operating within expected timeframes. Our team will continue to monitor the environment as part of standard operations. We appreciate your patience and understanding throughout this incident. This incident has been resolved.

Read the full incident report →

Started Jun 09, 2026, 04:03 PM UTC· resolved Jun 09, 2026, 04:42 PM UTC

1. monitoring Jun 09, 2026, 04:03 PM UTC

   We are investigating reports of connectivity issues affecting multiple services. Our teams have implemented a fix, and services are beginning to recover. We will provide our next update within 30 minutes, or sooner if additional information becomes available.

2. monitoring Jun 09, 2026, 04:19 PM UTC

   Connectivity issues have been resolved, and we are currently monitoring to ensure system stability. We'll post our next update in 30 minutes, if not sooner.

3. resolved Jun 09, 2026, 04:42 PM UTC

   We are no longer experiencing connectivity issues. This event is now resolved, and the system is operating normally. Thank you for your patience and understanding.

Read the full incident report →

Started Jun 05, 2026, 07:30 AM UTC· resolved Jun 05, 2026, 08:40 AM UTC

1. resolved Jun 05, 2026, 09:18 AM UTC

   The issue affecting new product activations and renewals has been resolved. Between 7:30 AM UTC and 8:40 AM UTC, some delays were observed due to a backlog in the processing queue. The backlog has now been fully cleared, and services within WatchGuard Cloud are operating normally. Our teams will continue to monitor the system to ensure ongoing stability. Thank you for your patience and understanding while we worked to resolve this issue.

Read the full incident report →

Started May 22, 2026, 04:49 AM UTC· resolved May 22, 2026, 01:11 PM UTC

1. identified May 22, 2026, 04:49 AM UTC

   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.

2. monitoring May 22, 2026, 11:48 AM UTC

   Our systems show that reports of errors during migration to DNSWatch in WGC are returning to normal and we're monitoring to ensure system stability. We'll post our next update in approximately 60 minutes, if not sooner.

3. resolved May 22, 2026, 01:11 PM UTC

   We are no longer experiencing errors during migration to DNSWatch in WGC and this incident is now resolved. The system is operating normally at this time.

Read the full incident report →

Started May 04, 2026, 01:32 PM UTC· resolved May 04, 2026, 11:23 PM UTC

1. identified May 04, 2026, 01:32 PM UTC

   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.

2. identified May 04, 2026, 02:50 PM UTC

   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.

3. identified May 04, 2026, 04:52 PM UTC

   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.

4. identified May 04, 2026, 06:54 PM UTC

   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.

5. monitoring May 04, 2026, 10:52 PM UTC

   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.

6. resolved May 04, 2026, 11:23 PM UTC

   This incident has been resolved and the service is operating normally at this time. Again, we apologize for any impact this may have had on you or your customers.

Read the full incident report →

Started May 01, 2026, 06:57 PM UTC· resolved May 02, 2026, 02:40 AM UTC

1. investigating May 01, 2026, 06:57 PM UTC

   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.

2. identified May 01, 2026, 08:00 PM UTC

   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.

3. identified May 01, 2026, 08:19 PM UTC

   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.

4. identified May 02, 2026, 12:30 AM UTC

   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.

5. monitoring May 02, 2026, 02:09 AM UTC

   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.

6. resolved May 02, 2026, 02:40 AM UTC

   We are no longer experiencing delays in our service and this event is now resolved. The service is operating normally at this time, Thank you for your patience and understanding.

Read the full incident report →

Started Apr 29, 2026, 06:35 AM UTC· resolved Apr 29, 2026, 07:54 AM UTC

1. investigating Apr 29, 2026, 06:35 AM UTC

   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.

2. identified Apr 29, 2026, 06:36 AM UTC

   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.

3. monitoring Apr 29, 2026, 07:25 AM UTC

   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.

4. resolved Apr 29, 2026, 07:54 AM UTC

   We are no longer experiencing issues with the System Management console and this incident is now resolved. The services are operating normally at this time. Again, we apologize for any impact this may have had on you or your customers.

Read the full incident report →

Started Apr 24, 2026, 10:00 AM UTC· resolved Apr 24, 2026, 03:28 PM UTC

1. identified Apr 24, 2026, 10:00 AM UTC

   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.

2. identified Apr 24, 2026, 11:02 AM UTC

   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.

3. identified Apr 24, 2026, 12:01 PM UTC

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

4. identified Apr 24, 2026, 01:02 PM UTC

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

5. monitoring Apr 24, 2026, 02:52 PM UTC

   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.

6. resolved Apr 24, 2026, 03:28 PM UTC

   We have completed monitoring following the earlier issues affecting Local AuthPoint users with RADIUS MSCHAPv2 authentication. All systems are operating normally at this time, and the incident is fully resolved. We apologize for any inconvenience this may have caused to you or your customers.

Read the full incident report →

Started Apr 21, 2026, 12:39 PM UTC· resolved Apr 28, 2026, 05:08 AM UTC

1. investigating Apr 21, 2026, 12:39 PM UTC

   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.

2. identified Apr 21, 2026, 02:55 PM UTC

   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.

3. identified Apr 21, 2026, 09:08 PM UTC

   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.

4. identified Apr 22, 2026, 01:13 AM UTC

   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.

5. identified Apr 22, 2026, 04:03 PM UTC

   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.

6. identified Apr 22, 2026, 08:03 PM UTC

   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.

7. identified Apr 23, 2026, 02:22 AM UTC

   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.

8. identified Apr 23, 2026, 08:03 AM UTC

   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.

9. identified Apr 23, 2026, 07:56 PM UTC

   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.

10. identified Apr 24, 2026, 01:51 AM UTC

    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.

11. identified Apr 24, 2026, 08:49 AM UTC

    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

12. identified Apr 24, 2026, 08:08 PM UTC

    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.

13. identified Apr 27, 2026, 08:00 PM UTC

    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.

14. identified Apr 27, 2026, 11:03 PM UTC

    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

15. resolved Apr 28, 2026, 05:08 AM UTC

    The delays in incident persistence have been resolved. During this incident, a small subset of accounts may have experienced gaps in event processing. We are conducting a full post-event review, and a full RCA will be available upon request once complete. We apologize for any impact this may have had on your business.

Read the full incident report →

Started Apr 20, 2026, 04:03 PM UTC· resolved Apr 20, 2026, 07:05 PM UTC

1. identified Apr 20, 2026, 04:03 PM UTC

   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.

2. monitoring Apr 20, 2026, 06:34 PM UTC

   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.

3. resolved Apr 20, 2026, 07:05 PM UTC

   This incident has been resolved and the service is operating normally at this time. We apologize for any impact this may have had on you or your customers.

Read the full incident report →

Started Apr 17, 2026, 10:08 AM UTC· resolved Apr 17, 2026, 03:08 PM UTC

1. identified Apr 17, 2026, 10:08 AM UTC

   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.

2. identified Apr 17, 2026, 12:58 PM UTC

   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.

3. monitoring Apr 17, 2026, 02:02 PM UTC

   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.

4. resolved Apr 17, 2026, 03:08 PM UTC

   We are no longer experiencing delays in our Visibility Reporting service and this event is now resolved. The service is operating normally at this time.

Read the full incident report →

Started Apr 16, 2026, 09:00 PM UTC· resolved Apr 18, 2026, 08:03 AM UTC

1. identified Apr 16, 2026, 09:00 PM UTC

   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.

2. identified Apr 16, 2026, 09:59 PM UTC

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

3. identified Apr 17, 2026, 12:46 AM UTC

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

4. identified Apr 17, 2026, 02:57 AM UTC

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

5. identified Apr 17, 2026, 07:02 AM UTC

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

6. identified Apr 17, 2026, 12:59 PM UTC

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

7. identified Apr 17, 2026, 06:51 PM UTC

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

8. identified Apr 18, 2026, 01:12 AM UTC

   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.

9. identified Apr 18, 2026, 07:00 AM UTC

   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.

10. monitoring Apr 18, 2026, 07:30 AM UTC

    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.

11. resolved Apr 18, 2026, 08:03 AM UTC

    The issue affecting DNSWatch dashboard performance has been fully resolved. The service is operating normally at this time.

Read the full incident report →

Started Apr 15, 2026, 01:45 PM UTC· resolved Apr 16, 2026, 11:54 PM UTC

1. identified Apr 15, 2026, 01:45 PM UTC

   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.

2. identified Apr 15, 2026, 03:01 PM UTC

   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.

3. identified Apr 15, 2026, 04:06 PM UTC

   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.

4. identified Apr 15, 2026, 06:04 PM UTC

   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.

5. identified Apr 15, 2026, 09:16 PM UTC

   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.

6. identified Apr 16, 2026, 12:07 AM UTC

   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.

7. identified Apr 16, 2026, 08:34 AM 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.

8. identified Apr 16, 2026, 02:26 PM UTC

   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.

9. identified Apr 16, 2026, 08:14 PM UTC

   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.

10. monitoring Apr 16, 2026, 11:00 PM UTC

    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.

11. resolved Apr 16, 2026, 11:54 PM UTC

    We are no longer experiencing delays in our Visibility Reporting service and this event is now resolved. The service is operating normally at this time.

Read the full incident report →

Started Apr 10, 2026, 05:15 PM UTC· resolved Apr 10, 2026, 07:40 PM UTC

1. investigating Apr 10, 2026, 05:15 PM UTC

   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.

2. identified Apr 10, 2026, 05:24 PM UTC

   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.

3. monitoring Apr 10, 2026, 06:24 PM UTC

   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.

4. monitoring Apr 10, 2026, 06:52 PM UTC

   The fix is still actively being deployed and we continue to monitor. We'll post our next update in 30 minutes, if not sooner.

5. monitoring Apr 10, 2026, 07:16 PM UTC

   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.

6. resolved Apr 10, 2026, 07:40 PM UTC

   We are no longer experiencing issues while creating accounts via our public API, and this event is now resolved. The service is operating normally at this time.

Read the full incident report →

Started Apr 02, 2026, 07:01 PM UTC· resolved Apr 02, 2026, 08:18 PM UTC

1. investigating Apr 02, 2026, 07:01 PM UTC

   We are investigating issues with Zero-touch deployments for new Fireboxes. We'll post an update within the next 30 minutes.

2. identified Apr 02, 2026, 07:39 PM UTC

   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.

3. monitoring Apr 02, 2026, 07:39 PM UTC

   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.

4. resolved Apr 02, 2026, 08:18 PM UTC

   We are no longer experiencing issues with new Firebox deployments using the zero-touch method, and this incident is now resolved. The service is operating normally at this time.

Read the full incident report →

Started Apr 02, 2026, 08:59 AM UTC· resolved Apr 02, 2026, 12:42 PM UTC

1. investigating Apr 02, 2026, 08:59 AM UTC

   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.

2. identified Apr 02, 2026, 09:10 AM UTC

   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.

3. monitoring Apr 02, 2026, 09:18 AM UTC

   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.

4. identified Apr 02, 2026, 09:41 AM UTC

   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.

5. monitoring Apr 02, 2026, 10:45 AM UTC

   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.

6. monitoring Apr 02, 2026, 11:13 AM UTC

   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.

7. resolved Apr 02, 2026, 12:42 PM UTC

   We are no longer experiencing reports of errors affecting the DNSWatch service and this incident is now resolved. The service is operating normally at this time.

Read the full incident report →

Started Apr 01, 2026, 06:38 PM UTC· resolved Apr 02, 2026, 06:15 PM UTC

1. investigating Apr 01, 2026, 06:38 PM UTC

   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.

2. identified Apr 01, 2026, 07:47 PM UTC

   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.

3. identified Apr 01, 2026, 10:29 PM UTC

   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.

4. identified Apr 02, 2026, 02:41 AM UTC

   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.

5. identified Apr 02, 2026, 06:38 AM UTC

   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

6. monitoring Apr 02, 2026, 04:43 PM UTC

   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.

7. monitoring Apr 02, 2026, 05:43 PM UTC

   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

8. resolved Apr 02, 2026, 06:15 PM UTC

   The issue affecting new product activations and renewals has been resolved. The backlog queue has been fully processed, and services within WatchGuard Cloud are operating normally. Our teams will continue to monitor the system to ensure ongoing stability. Thank you for your patience and understanding while we worked to resolve this issue.

Read the full incident report →