WatchGuard

Recent incidents

1. 2026-06-10 - GLOBAL - WatchGuard Endpoint Security issues

   Major · 10 Jun 2026, 14:55 · resolved about 3 hours ago

   • resolved11 Jun, 04:22

     Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

   • investigating11 Jun, 04:20

     Jun 10, 23:29 UTC Update - 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. Jun 10, 19:47 UTC Update - 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 Jun 10, 17:29 UTC Monitoring - 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. Jun 10, 15:37 UTC Update - 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. Jun 10, 14:21 UTC Identified - 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. Jun 10, 13:55 UTC Investigating - 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.

   • resolved11 Jun, 04:10

     Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

   • investigating11 Jun, 00:30

     Jun 10, 23:29 UTC Update - 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. Jun 10, 19:47 UTC Update - 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 Jun 10, 17:29 UTC Monitoring - 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. Jun 10, 15:37 UTC Update - 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. Jun 10, 14:21 UTC Identified - 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. Jun 10, 13:55 UTC Investigating - 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.

   • investigating10 Jun, 20:48

     Jun 10, 19:47 UTC Update - 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 Jun 10, 17:29 UTC Monitoring - 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. Jun 10, 15:37 UTC Update - 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. Jun 10, 14:21 UTC Identified - 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. Jun 10, 13:55 UTC Investigating - 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.

   • investigating10 Jun, 18:30

     Jun 10, 17:29 UTC Monitoring - 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. Jun 10, 15:37 UTC Update - 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. Jun 10, 14:21 UTC Identified - 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. Jun 10, 13:55 UTC Investigating - 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.

   • investigating10 Jun, 16:38

     Jun 10, 15:37 UTC Update - 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. Jun 10, 14:21 UTC Identified - 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. Jun 10, 13:55 UTC Investigating - 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.

   • investigating10 Jun, 15:22

     Jun 10, 14:21 UTC Identified - 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. Jun 10, 13:55 UTC Investigating - 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.

   • investigating10 Jun, 14:56

     Jun 10, 13:55 UTC Investigating - 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. 2026-06-09 - GLOBAL - Connectivity issues across several services

   Major · 9 Jun 2026, 17:03 · resolved 1 day ago

   • resolved9 Jun, 17:44

     Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

   • investigating9 Jun, 17:20

     Jun 9, 16:19 UTC Update - 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. Jun 9, 16:03 UTC Monitoring - 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.

   • investigating9 Jun, 17:04

     Jun 9, 16:03 UTC Monitoring - 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.

3. Managed Services Maintenance - Global

   Maintenance · 6 Jun 2026, 18:00 · resolved 4 days ago

   • resolved6 Jun, 23:08

     Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

   • investigating6 Jun, 23:06

     Jun 6, 17:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Apr 24, 11:35 UTC Scheduled - On June 6, 2026, starting at 17:00 UTC, Managed services Data Ingestion will undergo a maintenance in all regions, the maintenance window is expected to last 5 hours. Impact: During this window, there may be temporary delays in alert processing for certain cloud-based integrations. Following the maintenance, systems will be fully validated and normal operations will resume. Any delayed data will be processed in accordance with standard procedures. We recommend customers follow their usual security best practices during this time. We apologize for any inconvenience and appreciate your understanding and cooperation. If you have any questions or need further assistance, please do not hesitate to contact our support team.

   • resolved6 Jun, 23:00

     Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

   • investigating6 Jun, 18:00

     Jun 6, 17:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Apr 24, 11:35 UTC Scheduled - On June 6, 2026, starting at 17:00 UTC, Managed services Data Ingestion will undergo a maintenance in all regions, the maintenance window is expected to last 5 hours. Impact: During this window, there may be temporary delays in alert processing for certain cloud-based integrations. Following the maintenance, systems will be fully validated and normal operations will resume. Any delayed data will be processed in accordance with standard procedures. We recommend customers follow their usual security best practices during this time. We apologize for any inconvenience and appreciate your understanding and cooperation. If you have any questions or need further assistance, please do not hesitate to contact our support team.

   • investigating6 Jun, 17:00

     THIS IS A SCHEDULED EVENT Jun 6, 17:00 - 22:00 UTC Apr 24, 11:35 UTC Scheduled - On June 6, 2026, starting at 17:00 UTC, Managed services Data Ingestion will undergo a maintenance in all regions, the maintenance window is expected to last 5 hours. Impact: During this window, there may be temporary delays in alert processing for certain cloud-based integrations. Following the maintenance, systems will be fully validated and normal operations will resume. Any delayed data will be processed in accordance with standard procedures. We recommend customers follow their usual security best practices during this time. We apologize for any inconvenience and appreciate your understanding and cooperation. If you have any questions or need further assistance, please do not hesitate to contact our support team.

4. 2026-05-22 - GLOBAL - WGC DNSWatch Migration Failures

   Major · 22 May 2026, 05:49 · resolved 20 days ago

   • resolved22 May, 14:12

     Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

   • investigating22 May, 12:48

     May 22, 11:48 UTC Monitoring - 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. May 22, 04:49 UTC Identified - 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.

   • investigating22 May, 09:04

     May 22, 04:49 UTC Identified - 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.

   • investigating22 May, 05:50

     May 22, 04:49 UTC Identified - 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.