Live  /  Providers  /  WatchGuard Technologies

WatchGuard Technologies

watchguard.comReporting incidents

Independent assessment — SquidGrid is not affiliated with WatchGuard Technologies. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

SaaS & business software · SquidGrid tracks WatchGuard Technologies’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what WatchGuard Technologies is reporting

Current & recent incidents

identified

2026-09-30 - AMER - Device Summary and Dashboard errors

Major impact · 2026-09-30 18:31 UTC

Resolved

2026-09-25 Global - WatchGuard Cloud Operators list not loading

Major impact · 2026-09-25 22:23 UTC

Resolved

2026-09-08 - AMER - Mexico/Central FireCloud PoP connection issue

Major impact · 2026-09-09 20:31 UTC

Resolved

2026-09-04 - AMER - Mexico/Central FireCloud PoP connection issue

Major impact · 2026-09-04 21:32 UTC

Resolved

2026-09-03 - AMER - FireCloud PoP issue

Major impact · 2026-09-04 05:41 UTC

Mirrored from the provider’s own published status. Times in UTC.

Independent path health

A status page tells you what WatchGuard Technologies has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

WatchGuard Technologies runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of WatchGuard Technologies is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with WatchGuard Technologies.