Minor incident

WatchGuard Technologies: 2026-10-23 - EMEA - ThreatSync delays in incident persistence

Affected: Incident Persistence:::EMEA

Current status of WatchGuard Technologies: Operational — live WatchGuard Technologies status

Timeline

1. Oct 23, 2026, 17:03 UTC
   investigating
   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.
2. Oct 23, 2026, 18:19 UTC
   identified
   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.
3. Oct 23, 2026, 19:25 UTC
   identified
   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.
4. Oct 23, 2026, 21:06 UTC
   identified
   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.
5. Oct 23, 2026, 22:46 UTC
   identified
   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.
6. Oct 24, 2026, 02:46 UTC
   identified
   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.
7. Oct 24, 2026, 06:53 UTC
   identified
   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.
8. Oct 24, 2026, 12:38 UTC
   identified
   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
9. Oct 24, 2026, 14:15 UTC
   identified
   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. We will provide our next update on October 24 at 20:30 UTC, if not sooner. Thank you for your patience and understanding.
10. Oct 24, 2026, 20:22 UTC
    monitoring
    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 1 hour, if not sooner. Thank you for your continued patience.
11. Oct 24, 2026, 21:26 UTC
    resolved
    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.

Updates as published by WatchGuard Technologies (original).