Is WatchGuard down?

We are investigating delays in incident persistence. Once we determine the impact and scale of these we'll post our next update in 60 minutes, if not sooner.

We have identified the cause of the delays affecting incident persistence and are working to mitigate the issue. Incident data may be delayed in appearing in the UI. We will provide our next update in 60 minutes, or sooner. We apologize for any impact this may have had on you or your customers.

We are continuing to work on resolving the delays affecting incident persistence. We will provide our next update in 2 hours, if not sooner. Thank you for your patience.

A fix has been implemented and we are monitoring recovery to ensure incident persistence returns to normal. We will provide our next update in 2 hours, if not sooner. Thank you for your patience.

We are continuing to actively work on the incident persistence issue, and recovery efforts are ongoing. We are closely monitoring progress and working to restore normal operation. We will provide our next update in 4 hours, if not sooner. Thank you for your continued patience.

We are continuing to actively work on resolving the incident persistence issue, and recovery efforts remain ongoing. We are closely monitoring the situation and working toward full recovery. We will post our next update on October 24 at 6:30 UTC, if not sooner. Thank you for your continued patience and understanding.

We continue to monitor the recovery process. The next update will be shared on October 24th at 12:30UTC, or earlier if warranted. Thank you for your continued patience. Thank you for your patience.

Our team continues to work actively on resolving the incident persistence issue. Mitigation measures are in place, and current metrics indicate improved processing times and reduced delays. While recovery is still in progress, we are closely monitoring the environment and working toward full resolution. We will provide our next update on October 24 at 18:30 UTC, or sooner if additional information becomes available. Thank you for your patience and understanding

To mitigate processing delays, we are temporarily skipping the persistence of Botnet Signals data. This change is expected to restore normal processing times while we continue working on a permanent fix. We will continue to monitor the situation and provide updates as progress is made.

Our systems show that incident persistence is returning to normal, and we are continuing to monitor the system to ensure stability. We will provide our next update in 30 minutes, if not sooner. Thank you for your continued patience.

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.

We're investigating unexpected validation errors when attempting to add new WatchGuard Cloud Operators or update existing WatchGuard Cloud Operators. Once we determine the impact and scale of this issue. We'll post our next update in 30 minutes, if not sooner.

We are continuing to investigate this issue. Attempting to add or modify a WatchGuard Cloud operator will result in an unexpected "Must select at least one account group" error. We'll post our next update in 30 minutes, if not sooner.

We are no longer experiencing unexpected validation errors when adding or updating WatchGuard Cloud Operators, and this incident is now resolved. Operator management in WatchGuard Cloud is operating normally at this time. We apologize for any impact this may have had on you or your customers.

We're investigating an issue preventing customers from accessing the DNSWatch v1 portal at dnswatch.watchguard.com. Users may encounter HTTP 500 errors when attempting to load the portal. Our teams are investigating the issue and working to identify the cause. We apologize for the inconvenience and will provide another update within 60 minutes, or sooner if additional information becomes available.

We're continuing to investigate the issue preventing customers from accessing the DNSWatch v1 portal at dnswatch.watchguard.com. Users may encounter HTTP 500 errors when attempting to load the portal. Our teams are actively investigating and working to restore normal access. We apologize for the inconvenience and will provide our next update within 2 hours, or sooner if additional information becomes available.

We are continuing to investigate this issue.

The DNSWatch v1 portal is coming back online following remediation by our engineering team. We are monitoring the service to ensure that access is fully restored and the portal remains stable. We apologize for the inconvenience and will provide our next update within 30 minutes, or sooner if further information becomes available.

This incident is now resolved. The system is operating normally at this time.

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

We continue to work on alerts on Web UI Login 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.

Our systems show alerts on Web UI Login 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.

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

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

We continue to work on alerts on DNSWatch V1 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 30 minutes, if not sooner.

Our systems show alerts on DNSWatch V1 services are returning to normal and we're monitoring to ensure system stability. We'll post our next update in 30 minutes, if not sooner.

We are no longer experiencing alerts on DNSWatch V1 services and this incident is now resolved. The system is operating normally at this time.