Live / WatchGuard Technologies / Incident
WatchGuard Technologies: 2026-10-23 - EMEA - ThreatSync delays in incident persistence
WatchGuard Technologies · watchguard.comMinor incidentResolved2026-10-24 21:26 UTC
Public — what happened
Summary
WatchGuard Technologies reported a minor issue in the EMEA region in which ThreatSync was slow to save incident data, so new incidents could take a while to show up in the interface. The problem began on October 23 at 17:03 UTC, and the company said it found the cause about an hour later, though it did not describe what that cause was. After a first fix on the evening of October 23, recovery continued into the next day, and on October 24 it said it was temporarily not saving Botnet Signals data to bring processing times back to normal while a permanent fix was developed. WatchGuard said processing was returning to normal by 20:22 UTC on October 24, and the incident is now marked resolved.
Affected
Incident Persistence:::EMEA
Timeline
- Started — 2026-10-23 17:03 UTC
- Investigating — 2026-10-23 17:03 UTC
- Identified — 2026-10-23 18:19 UTC (8 updates)
- Monitoring — 2026-10-24 20:22 UTC
- Resolved — 2026-10-24 21:26 UTC · 28h 23m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach WatchGuard Technologies against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for WatchGuard Technologies: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the WatchGuard Technologies report →
More from WatchGuard Technologies
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.