WatchGuard experienced a minor incident on January 22, 2026 affecting Health and Connectivity:::AMER and Health and Connectivity:::EMEA and 1 more component, lasting 6h 23m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jan 22, 2026, 02:15 PM UTC
We have identified an issue impacting FireCloud PoPs. Our teams are actively working to fix root cause, after a security update to the FireCloud PoPs caused an issue with healthy and connectivity. Regions are being refreshed and connectivity should be established as soon as possible. We'll post our next update in 1 hour, if not sooner.
- identified Jan 22, 2026, 03:19 PM UTC
We are still working hard to resolve this event. Please check back in 1 hour for updates. Thanks for your patience.
- identified Jan 22, 2026, 04:45 PM UTC
Our team is actively working to restore the FireCloud Health and Connectivity service to normal operations. Please check back in one hour for further updates.
- identified Jan 22, 2026, 05:40 PM UTC
Our team continues to actively work on restoring the FireCloud Health and Connectivity service to normal operations. We will post our next update within two hours.
- identified Jan 22, 2026, 07:30 PM UTC
Our team continues to actively work on restoring the FireCloud Health and Connectivity service to normal operations. We will post our next update within two hours.
- resolved Jan 22, 2026, 08:39 PM UTC
FireCloud Health and Connectivity are now restored to normal operations. This is now resolved. We apologize for any inconvenience that this may have had on you.
- postmortem Jan 30, 2026, 07:15 PM UTC
Initial Event Summary: The WatchGuard FireCloud PoPs experienced a service disruption in all Global regions approximately between January 22nd 12:31 UTC to 20:00 UTC. This resulted in the FireCloud PoPs becoming unhealthy and unable to accept connections from FireCloud clients. The event is now resolved, and all FireCloud services are now operating normally for all users. Initial Event Findings: At approximately 12:31 UTC on Jan 22, 2026 our on-call engineers were alerted to a potential issue in the Americas region and found that the issue spanned to all Global regions. During our investigation, monitoring indicated that our PoP's network connectivity had dropped to zero indicating no clients connected. After further investigation, our team discovered that an automatic 3rd party infrastructure provider security update resulted in critical PoP services being unable to communicate. As a result, the FireCloud clients could authenticate but not establish connections to FireCloud PoPs. Our teams worked to mitigate the impact by deploying healthy PoPs and adjusting FireCloud data as needed to allow for successful client connection. At approximately 20:00 UTC, the FireCloud Global PoPs were restored to a healthy state and the FireCloud clients could successfully connect to FireCloud. Moving Forward: Our team will evaluate and test 3rd party infrastructure provider security updates manually prior to deployment. We are in communication with the 3rd party infrastructure provider to address the impact of this event. We sincerely apologize for the impact on our affected customers and we know the stability of the FireCloud is important to you and your business. At WatchGuard, we will never be satisfied with any events that impact our customer operations and we will continue to do everything we can to drive improvements across our services.