WatchGuard incident

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

Resolved after 8 hours 21 minutes, affecting Dashboard:::GLOBE and Content Filtering:::GLOBE, on May 22, 2026.

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.

Started
May 22, 2026, 04:49 AM UTC
Resolved
May 22, 2026, 01:11 PM UTC
Duration
8h 21m
Detected by Pingoru
May 22, 2026, 04:49 AM UTC

Affected components

Dashboard:::GLOBEContent Filtering:::GLOBE

Update timeline

  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.

Your product runs on more than WatchGuard

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →