2026-05-22 - GLOBAL - WGC DNSWatch Migration Failures
Major · resolved · started 22 May 2026, 05:49 · resolved 22 May 2026, 14:12
resolved · 22 May 2026, 14:12
Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.
investigating · 22 May 2026, 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.
investigating · 22 May 2026, 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.
investigating · 22 May 2026, 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.