- Detected by Pingoru
- Sep 30, 2026, 05:52 PM UTC
- Resolved
- Sep 30, 2026, 09:52 PM UTC
- Duration
- 4h
Affected: Dashboards and Reports:::AMER
Timeline · 4 updates
-
investigating Sep 30, 2026, 05:52 PM UTC
We’re investigating reports of errors when attempting to view device status and device dashboards in WatchGuard Cloud. Once we determine the impact and scope of these potential issues, we’ll post our next update in 30 minutes, if not sooner.
-
identified Sep 30, 2026, 06:31 PM UTC
We continue to work on the device status and dashboard issues in WatchGuard Cloud. 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 30 minutes, if not sooner.
-
monitoring Sep 30, 2026, 07:18 PM UTC
Service adjustments have been made to the WatchGuard Cloud reporting systems. Device summaries and dashboards are now loading; however, some reports or dashboard elements may take longer than expected to load while we process the backlog generated during the incident. Our team is actively monitoring the environment and working to ensure all queued items are processed as quickly as possible. We appreciate your patience and understanding throughout this incident. We will continue to monitor the situation and provide further updates in next 2 hours.
-
resolved Sep 30, 2026, 09:52 PM UTC
Device summaries and dashboards are now loading without delay, and this incident is now resolved. Again, we apologize for any impact this may have had on you or your customers.
Read the full incident report →
- Detected by Pingoru
- Sep 25, 2026, 09:49 PM UTC
- Resolved
- Sep 25, 2026, 10:23 PM UTC
- Duration
- 34m
Affected: Operator Administration:::AMEROperator Administration:::EMEAOperator Administration:::APAC
Timeline · 2 updates
-
identified Sep 25, 2026, 09:49 PM UTC
At approximately 21:00:00 UTC time, the certificate used by the WatchGuard Cloud users and groups API expired. As a result, WatchGuard Cloud administrators are unable to view, update or manage their WatchGuard Cloud Operators. Our team has already renewed the certificate and is actively deploying it to all regions. We'll post our next update in 30 minutes, if not sooner.
-
resolved Sep 25, 2026, 10:23 PM UTC
The updated WatchGuard Cloud user and group API certificate has been successfully deployed to all regions as of 22:20:00 UTC. Services are operating normally at this time. We appreciate your continued patience and apologize again for any impact this may have had on you or your customers.
Read the full incident report →
- Detected by Pingoru
- Sep 08, 2026, 04:08 PM UTC
- Resolved
- Sep 14, 2026, 08:28 AM UTC
- Duration
- 5d 16h
Affected: Authentication:::AMERHealth and Connectivity:::AMER
Timeline · 6 updates
-
investigating Sep 08, 2026, 04:08 PM UTC
Some customers are experiencing connectivity issues affecting the Mexico/Central Point of Presence (PoP). Our engineering team is actively investigating the issue. We will provide another update within the next 60 minutes as more information becomes available. We apologize for any impact this may be causing to customers. This issue is affecting connectivity through the Mexico/Central PoP only."
-
investigating Sep 08, 2026, 05:00 PM UTC
We continue to work on connectivity issues the Mexico/Central Point of Presence (PoP). Infrastructure updates are being deployed to the affected region. The deployment will take between 15 and 30 minutes to complete. Any connected client to the affected PoP will briefly disconnect while the deployment takes place. We apologize for any impact this may be causing to customers. We'll post our next update in 60 minutes, if not sooner.
-
monitoring Sep 08, 2026, 06:07 PM UTC
WatchGuard deployed infrastructure updates to the Mexico/Central Point of Presence (PoP). Our engineering team is monitoring and will continue to investigate the issue. We will provide another update within the next 4 hours as more information becomes available. We apologize for any impact this may have caused your customers.
-
monitoring Sep 08, 2026, 10:08 PM UTC
FireCloud services in Mexico/Central Point of Presence (PoP) region are operating normally after the infrastructure updates deployed earlier today. Our engineering team continues to monitor the services in the region to ensure long-term stability. We will provide another update within the next 24 hours. We apologize for any impact this may have caused your customers. This issue affected the Mexico/Central PoP only.
-
monitoring Sep 09, 2026, 08:31 PM UTC
All FireCloud services in Mexico/Central Point of Presence (PoP) are operational, and there are no reported connectivity issues. Customers experiencing authentication or connectivity issues to the Mexico/Central PoP are encouraged to contact WatchGuard Support for assistance. Our engineering team continues to monitor the services in the region to ensure long-term stability.
-
resolved Sep 14, 2026, 08:28 AM UTC
We are no longer experiencing connectivity issues affecting the Mexico/Central Point of Presence (PoP), and this incident is now resolved. Service is operating normally at this time. We apologize for any impact this incident may have caused you or your customers and thank you for your patience while our teams worked to restore service.
Read the full incident report →
- Detected by Pingoru
- Sep 04, 2026, 05:16 PM UTC
- Resolved
- Sep 05, 2026, 01:45 AM UTC
- Duration
- 8h 28m
Affected: Authentication:::AMERHealth and Connectivity:::AMER
Timeline · 7 updates
-
investigating Sep 04, 2026, 05:16 PM UTC
Some customers are experiencing connectivity issues affecting the Mexico/Central Point of Presence (PoP) related to the handling of policies. Our engineering team is actively investigating the issue. We will provide another update within the next hour as more information becomes available. We apologize for any impact this may be causing to customers. This issue is affecting connectivity through the Mexico/Central PoP only.
-
investigating Sep 04, 2026, 06:23 PM UTC
We continue to work on the connectivity and policy handling issues affecting the Mexico/Central Point of Presence (PoP). The FireCloud Engineering team is preparing to make infrastructure changes to make the policy handling more reliable in this region. We'll post our next update in 60 minutes, if not sooner.
-
investigating Sep 04, 2026, 06:51 PM UTC
We continue to work on connectivity issues affecting the Mexico/Central Point of Presence (PoP). Infrastructure updates to the policy handling service will start at 19:00 UTC time and will take approximately 15 to 30 minutes to complete. FireCloud clients connected to the affected PoP region will disconnect and reconnect momentarily while the changes are being deployed. We'll post our next update in 60 minutes, if not sooner.
-
investigating Sep 04, 2026, 06:53 PM UTC
We are continuing to investigate this issue.
-
investigating Sep 04, 2026, 08:14 PM UTC
We continue to work on connectivity issues and policy handling issues affecting the Mexico/Central Point of Presence (PoP). Infrastructure updates are being deployed to the affected region. We apologize for any impact this may be causing to customers. We'll post our next update in 60 minutes, if not sooner.
-
monitoring Sep 04, 2026, 09:32 PM UTC
WatchGuard deployed new infrastructure to increase capacity for users experiencing connectivity issues affecting the Mexico/Central Point of Presence (PoP) related to the handling of policies. Services our currently restored. Our engineering team continues monitoring and investigating the issue. We will provide another update within the next 4 hours as more information becomes available. We apologize for any impact this may have caused your customers. This issue was affecting connectivity through the Mexico/Central PoP only.
-
resolved Sep 05, 2026, 01:45 AM UTC
An infrastructure update was deployed in the Mexico/Central PoP to address the client scaling issues detected earlier today. We are no longer experiencing connectivity issues and policy handling issues in this region, and this incident is now resolved. We will continue to monitor the infrastructure to ensure the environment remains stable for clients.
Read the full incident report →
- Detected by Pingoru
- Sep 03, 2026, 05:11 PM UTC
- Resolved
- Sep 04, 2026, 06:08 AM UTC
- Duration
- 12h 57m
Affected: Authentication:::AMERHealth and Connectivity:::AMER
Timeline · 9 updates
Read the full incident report →
- Detected by Pingoru
- Sep 01, 2026, 04:41 PM UTC
- Resolved
- Sep 01, 2026, 04:41 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Sep 03, 2026, 02:09 PM UTC
On September 1, 2026, at 16:41 UTC, some customers began experiencing connectivity issues due to a problem affecting the Mexico/Central Point of Presence (PoP). Our engineering team worked to restore service, and the PoP returned to normal operation on September 2, 2026, at 11:44 UTC. We apologize for any impact this incident may have caused you or your customers. This issue affected connectivity through the Mexico/Central PoP only.
Read the full incident report →
- Detected by Pingoru
- Aug 26, 2026, 10:55 AM UTC
- Resolved
- Aug 26, 2026, 12:09 PM UTC
- Duration
- 1h 14m
Affected: Console:::EMEA
Timeline · 5 updates
-
investigating Aug 26, 2026, 10:55 AM UTC
We're investigating alerts on Endpoint console service. Once we determine the impact and scale of these errors we'll post our next update in 30 minutes, if not sooner.
-
investigating Aug 26, 2026, 11:28 AM UTC
We are still working hard to resolve this event. Please check back at 30 minutes for updates. Thanks for your patience.
-
identified Aug 26, 2026, 11:39 AM UTC
We continue to work on alerts on Endpoint console service and have identified the issue. 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 30 minutes, if not sooner.
-
monitoring Aug 26, 2026, 11:40 AM UTC
Our systems show alerts on Endpoint console service are returning to normal and we're monitoring to ensure system stability. We'll post our next update in 30 minutes, if not sooner.
-
resolved Aug 26, 2026, 12:09 PM UTC
We are no longer experiencing alerts on Endpoint console service and this incident is now resolved. The service is operating normally at this time.
Read the full incident report →
- Detected by Pingoru
- Aug 24, 2026, 07:15 PM UTC
- Resolved
- Aug 24, 2026, 08:13 PM UTC
- Duration
- 58m
Affected: Firebox Configuration:::AMER
Timeline · 3 updates
-
investigating Aug 24, 2026, 07:15 PM UTC
We’re investigating reports of errors when attempting to view Firebox configurations in WatchGuard Cloud. Once we determine the impact and scope of these potential issues, we’ll post our next update in 30 minutes, if not sooner.
-
monitoring Aug 24, 2026, 07:40 PM UTC
Our team has identified and deployed access rule mitigations for the errors encountered when attempting to view Firebox configurations in WatchGuard Cloud. We’ll continue to monitor the service to ensure system stability. We’ll post our next update in 30 minutes, if not sooner.
-
resolved Aug 24, 2026, 08:13 PM UTC
We are no longer experiencing reports of errors when attempting to view Firebox configurations in WatchGuard Cloud, and this incident is now resolved. Firebox Management in WatchGuard Cloud is operating normally at this time.
Read the full incident report →
- Detected by Pingoru
- Aug 24, 2026, 04:47 PM UTC
- Resolved
- Aug 24, 2026, 07:35 PM UTC
- Duration
- 2h 47m
Affected: RADIUS:::AMERSAML:::AMERLogon Agents:::AMER
Timeline · 4 updates
-
investigating Aug 24, 2026, 04:47 PM UTC
We have identified an issue affecting the AuthPoint Authentication service. Once we determine the impact and scale of these errors we'll post our next update in 30 minutes, if not sooner.
-
investigating Aug 24, 2026, 05:43 PM UTC
We are continuing to investigate an issue affecting the AuthPoint Authentication service. We apologize for the impact this event has caused. We’ll post our next update in 60 minutes, if not sooner.
-
monitoring Aug 24, 2026, 06:45 PM UTC
A fix has been implemented, and the AuthPoint Authentication service is returning to normal. During the incident, users may have experienced intermittent service disruptions. We are actively monitoring the service to ensure system stability. The issue was related to a central component responsible for internal communications that experienced a failure. We’ll post our next update in 60 minutes, if not sooner.
-
resolved Aug 24, 2026, 07:35 PM UTC
We are no longer experiencing issues with the AuthPoint Authentication service, and this incident is now resolved. The service is operating normally at this time. We apologize for any impact this may have had on you or your customers.
Read the full incident report →
- Detected by Pingoru
- Aug 17, 2026, 08:45 PM UTC
- Resolved
- Aug 17, 2026, 09:37 PM UTC
- Duration
- 52m
Affected: Administration:::GLOBEConsole:::GLOBE
Timeline · 3 updates
-
identified Aug 17, 2026, 08:45 PM UTC
Earlier today, our teams identified errors when accessing the Panda Endpoint Security Console. Users may have encountered errors when trying to access an incident or experienced intermittent access issues with the Orion threat hunting platform. A fix for this issue will be deployed shortly and we will post our next update in 30 minutes, if not sooner.
-
monitoring Aug 17, 2026, 09:10 PM UTC
Our systems show that errors when accessing the Panda Endpoint Security Console are returning to normal, and we're monitoring to ensure system stability. We'll post our next update in 30 minutes, if not sooner.
-
resolved Aug 17, 2026, 09:37 PM UTC
We are no longer experiencing errors when accessing the Panda Endpoint Security Console and this incident is now resolved. The service is operating normally at this time.
Read the full incident report →
- Detected by Pingoru
- Aug 17, 2026, 03:09 PM UTC
- Resolved
- Aug 17, 2026, 04:36 PM UTC
- Duration
- 1h 27m
Affected: Partner Portal:::CORE
Timeline · 4 updates
-
investigating Aug 17, 2026, 03:09 PM UTC
We're investigating errors logging into our Partner Portal. Once we determine the impact and scale of these errors, we'll post our next update in 30 minutes, if not sooner.
-
identified Aug 17, 2026, 03:21 PM UTC
We continue to work on errors when logging into our Partner Portal and have identified the issue to be related to dormant partner accounts. 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 60 minutes, if not sooner.
-
monitoring Aug 17, 2026, 04:09 PM UTC
Our systems show that errors logging into our Partner Portal are returning to normal and we're monitoring to ensure system stability. We'll post our next update in 30 minutes, if not sooner.
-
resolved Aug 17, 2026, 04:36 PM UTC
We are no longer experiencing errors logging into our Partner Portal and this event is now resolved. The service is operating normally at this time. We apologize for the impact this event has caused.
Read the full incident report →
- Detected by Pingoru
- Aug 13, 2026, 12:43 PM UTC
- Resolved
- Aug 13, 2026, 02:51 PM UTC
- Duration
- 2h 7m
Affected: Firebox Configuration:::EMEA
Timeline · 5 updates
-
investigating Aug 13, 2026, 12:43 PM UTC
We're investigating reports of errors while attempting to deploy Firebox Configurations in WatchGuard Cloud. Once we determine the impact and scale of these potential issues, we'll post our next update in 30 minutes, if not sooner.
-
investigating Aug 13, 2026, 01:12 PM UTC
We continue to investigate reports of errors while attempting to deploy Firebox Configurations in WatchGuard Cloud in our EMEA region. We'll post our next update in 30 minutes, if not sooner.
-
investigating Aug 13, 2026, 01:42 PM UTC
Our team is actively investigating reports of deployment errors related to Firebox Configurations in WatchGuard Cloud across the EMEA region. We will share our next update within 30 minutes, or earlier as new information becomes available.
-
monitoring Aug 13, 2026, 02:15 PM UTC
Our team has identified and deployed access rule mitigations for the errors while attempting to deploy Firebox Configurations in WatchGuard Cloud. We'll continue to monitor to ensure system stability. We'll post our next update in 30 minutes, if not sooner.
-
resolved Aug 13, 2026, 02:51 PM UTC
We are no longer experiencing reports of errors while attempting to deploy Firebox Configurations in WatchGuard Cloud in the EMEA region, and this incident is now resolved. Firebox Management in WatchGuard Cloud is operating normally at this time.
Read the full incident report →
- Detected by Pingoru
- Aug 13, 2026, 12:01 PM UTC
- Resolved
- Aug 13, 2026, 02:28 PM UTC
- Duration
- 2h 27m
Affected: Dashboards and Reports:::EMEA
Timeline · 3 updates
-
identified Aug 13, 2026, 12:01 PM UTC
We continue to make progress on the issue affecting the display of Signals statistics on the WatchGuard Cloud RAI dashboard. Recovery efforts remain underway as we continue processing the remaining backlog of queued data. We have observed a sustained reduction in the backlog, and recovery continues to progress. However, some Signals statistics may still appear delayed or incomplete while the remaining data is being processed. Our teams remain actively engaged and are closely monitoring recovery progress to fully restore normal operations. We apologize for the impact this issue has caused and appreciate your continued patience. We will provide our next update in 4 hours, if not sooner.
-
monitoring Aug 13, 2026, 01:32 PM UTC
The recovery process has been completed, and normal operations have been restored for the Signals statistics on the WatchGuard Cloud RAI dashboard. Our teams are continuing to closely monitor the service to ensure stability and confirm that all systems continue to operate as expected. We will provide our next update in 60 minutes, if not sooner.
-
resolved Aug 13, 2026, 02:28 PM UTC
We are no longer experiencing issues affecting the display of Signals statistics on the WatchGuard Cloud RAI dashboard, and this incident is now resolved. The recovery process has been completed, all queued data has been processed, and Signals statistics are displaying as expected. Following continued monitoring and validation, our teams have confirmed that normal operations have been fully restored across all production regions. We apologize for the impact this issue may have caused and thank you for your patience throughout this extended recovery effort.
Read the full incident report →
- Detected by Pingoru
- Aug 13, 2026, 10:29 AM UTC
- Resolved
- Aug 13, 2026, 11:52 AM UTC
- Duration
- 1h 22m
Affected: Console:::GLOBE
Timeline · 4 updates
-
investigating Aug 13, 2026, 10:29 AM UTC
We're investigating alerts related to Agent Installer download errors from the Console service. Once we determine the impact and scope of these errors, we'll provide our next update within 30 minutes, or sooner if more information becomes available.
-
identified Aug 13, 2026, 10:40 AM UTC
We continue to work on reports of Agent Installer download errors affecting Aether/Cytomic services and have identified the issue. 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 30 minutes, if not sooner.
-
monitoring Aug 13, 2026, 11:51 AM UTC
Our systems show reports of Agent Installer download errors affecting Aether/Cytomic services are returning to normal, and we're monitoring to ensure system stability. We'll post our next update in 30 minutes, if not sooner.
-
resolved Aug 13, 2026, 11:52 AM UTC
We are no longer experiencing reports of Agent Installer download errors affecting Aether/Cytomic services, and this incident is now resolved. The service is operating normally at this time.
Read the full incident report →
- Detected by Pingoru
- Aug 11, 2026, 01:40 PM UTC
- Resolved
- Aug 11, 2026, 02:19 PM UTC
- Duration
- 38m
Affected: DNSWatch V1 DNS Resolvers:::APAC
Timeline · 4 updates
-
investigating Aug 11, 2026, 01:40 PM UTC
We're investigating alerts on DNSWatch V1 services. Once we determine the impact and scale of these errors we'll post our next update in 30 minutes, if not sooner.
-
identified Aug 11, 2026, 01:50 PM UTC
We continue to work on alerts on DNSWatch V1 services and have identified the issue. 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 30 minutes, if not sooner.
-
monitoring Aug 11, 2026, 01:52 PM UTC
Our systems show alerts on DNSWatch V1 services are returning to normal and we're monitoring to ensure system stability. We'll post our next update in 30 minutes, if not sooner.
-
resolved Aug 11, 2026, 02:19 PM UTC
We are no longer experiencing alerts on DNSWatch V1 services and this incident is now resolved. The system is operating normally at this time.
Read the full incident report →
- Detected by Pingoru
- Aug 07, 2026, 01:08 PM UTC
- Resolved
- Aug 08, 2026, 06:28 AM UTC
- Duration
- 17h 19m
Affected: Console:::GLOBEConsole:::AMERConsole:::EMEAConsole:::APAC
Timeline · 7 updates
-
investigating Aug 07, 2026, 01:08 PM UTC
We are investigating an issue affecting Aether/Cytomic and EPDR, under the "Endpoint Access Enforcement" section. Customers may experience dashboards failing to load and an error popup being displayed.
-
investigating Aug 07, 2026, 02:17 PM UTC
We continue to investigate the issue affecting Aether/Cytomic and EPDR and will post our next update in 3 hours if not sooner.
-
investigating Aug 07, 2026, 05:15 PM UTC
Our investigation into the issue affecting Aether/Cytomic and EPDR under the Endpoint Access Enforcement section is ongoing. Customers may continue to experience dashboards failing to load and may encounter an error popup when accessing this section. Our engineering team is actively working to identify the root cause and restore normal functionality as quickly as possible. We appreciate your patience and will provide another update in 3 hours, or sooner if additional information becomes available.
-
investigating Aug 07, 2026, 09:12 PM UTC
The issue affecting Aether/Cytomic and EPDR is still under investigation. We will post our next update in 4 hours, or sooner if we have new information to report.
-
identified Aug 08, 2026, 01:17 AM UTC
We have identified the issue affecting Aether/Cytomic and EPDR and are continuing to work toward a resolution. Our team is actively addressing the identified issue and monitoring the situation closely. We will provide our next update within 6 hours, or sooner if there are any significant developments.
-
monitoring Aug 08, 2026, 05:58 AM UTC
A fix has been deployed, and the Aether/Cytomic and EPDR services have recovered. The services are currently operating normally, and we are actively monitoring to confirm continued stability. We apologize for the impact this may have had on you or your customers, our next update will be posted in 30 minutes, if not sooner.
-
resolved Aug 08, 2026, 06:28 AM UTC
We are no longer experiencing issues with Aether/Cytomic and EPDR services and this event is now resolved. Services are operating normally at this time. We appreciate your continued patience and apologize again for any impact this may have had on you or your customers.
Read the full incident report →
- Detected by Pingoru
- Jul 24, 2026, 01:58 PM UTC
- Resolved
- Jul 24, 2026, 03:01 PM UTC
- Duration
- 1h 2m
Affected: Firebox Configuration:::AMERFirebox Live Status:::AMERWatchGuard Cloud DNS Resolvers:::AMER
Timeline · 2 updates
-
monitoring Jul 24, 2026, 01:58 PM UTC
Between 11:07 UTC and 12:14 UTC, we identified and resolved an issue that impacted a subset of Firebox and DNS services in the AMER region, including Firebox Configuration, Firebox Live Status, and DNS services. The service is operating normally at this time and we are monitoring to ensure system stability. We apologize for the impact this may have had on you or your customers. Our next update will be posted in 60 minutes, if not sooner.
-
resolved Jul 24, 2026, 03:01 PM UTC
We are no longer experiencing alerts on Firebox and DNS services and this incident is now resolved. The service is operating normally at this time.
Read the full incident report →
- Detected by Pingoru
- Jul 24, 2026, 01:22 PM UTC
- Resolved
- Jul 24, 2026, 02:24 PM UTC
- Duration
- 1h 1m
Affected: RADIUS:::AMERSAML:::AMERLogon Agents:::AMERADFS:::AMERRDWeb:::AMERFirebox:::AMERAPI:::AMER
Timeline · 2 updates
-
monitoring Jul 24, 2026, 01:22 PM UTC
Between 11:07 UTC and 12:14 UTC, we identified and resolved an issue that impacted a subset of AuthPoint authentication requests using password-only or password + MFA authentication. The service is operating normally at this time and we are monitoring to ensure system stability. We apologize for the impact this may have had on you or your customers, our next update will be posted in 60 minutes, if not sooner.
-
resolved Jul 24, 2026, 02:24 PM UTC
We are no longer experiencing AuthPoint authentication services and this incident is now resolved. The service is operating normally at this time.
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2026, 03:31 PM UTC
- Resolved
- Jul 23, 2026, 08:30 PM UTC
- Duration
- 4h 59m
Affected: Web UI Login:::AMERWeb UI Login:::EMEAWeb UI Login:::APACWatchGuard.com SSO (WGID):::COREAccount and User Administration:::COREActivations:::CORE
Timeline · 7 updates
-
investigating Jul 23, 2026, 03:31 PM UTC
We're investigating alerts on activations & logging into WatchGuard Cloud. Once we determine the impact and scale of this potential issue we'll post our next update in 30 minutes, if not sooner.
-
investigating Jul 23, 2026, 03:58 PM UTC
We continue to work on alerts for activations, logins, and account creation on WatchGuard Cloud. We'll post our next update in 30 minutes, if not sooner.
-
identified Jul 23, 2026, 04:26 PM UTC
We continue to work on alerts for activations, logins, and account creation and have identified networking issues. 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 60 minutes, if not sooner.
-
identified Jul 23, 2026, 05:25 PM UTC
We continue to remediate the networking issues impacting activations, logins, and account creation in WatchGuard Cloud. Work remains ongoing across multiple teams as we focus on restoring service functionality. We appreciate your continued patience and will post our next update in 60 minutes, if not sooner.
-
identified Jul 23, 2026, 06:25 PM UTC
We continue to work on remediating the networking issues impacting activations, logins, and account creation in WatchGuard Cloud. The issue was caused by problems within our third-party infrastructure provider. Our teams continue working to restore full service functionality as quickly as possible. We appreciate your continued patience and apologize for the impact this event has caused. We'll post our next update in 60 minutes, if not sooner.
-
monitoring Jul 23, 2026, 07:24 PM UTC
We are beginning to see service recovery for activations, logins, and account creation in WatchGuard Cloud. Services are returning to normal, and we are monitoring to ensure system stability. The issue was caused by problems within our third-party infrastructure provider. We appreciate your continued patience and will post our next update in 60 minutes, if not sooner.
-
resolved Jul 23, 2026, 08:30 PM UTC
We are no longer experiencing issues with activations, logins, and account creation in WatchGuard Cloud, and this event is now resolved. Services are operating normally at this time. The issue was caused by problems within our third-party infrastructure provider. We appreciate your continued patience and apologize again for any impact this may have had on you or your customers.
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2026, 09:51 AM UTC
- Resolved
- Jul 23, 2026, 01:11 PM UTC
- Duration
- 3h 19m
Affected: Activations:::CORE
Timeline · 6 updates
-
investigating Jul 23, 2026, 09:51 AM UTC
We're investigating alerts on DNS Activation services. Once we determine the impact and scale of these errors we'll post our next update in 60 minutes, if not sooner.
-
investigating Jul 23, 2026, 10:59 AM UTC
We are still working hard to resolve this event. Please check back at 30 minutes for updates. Thanks for your patience.
-
identified Jul 23, 2026, 11:47 AM UTC
We continue to work on alerts on DNS Activation services and have identified the issue. 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 60 minutes, if not sooner.
-
monitoring Jul 23, 2026, 12:39 PM UTC
Our systems show alerts on DNS Activation service are returning to normal and we're monitoring to ensure system stability. We'll post our next update in 30 minutes, if not sooner.
-
monitoring Jul 23, 2026, 01:10 PM UTC
We are no longer experiencing alerts on DNS Activation service and this incident is now resolved. The service is operating normally at this time.
-
resolved Jul 23, 2026, 01:11 PM UTC
We are no longer experiencing alerts on DNS Activation service and this incident is now resolved. The service is operating normally at this time.
Read the full incident report →
- Detected by Pingoru
- Jul 06, 2026, 05:12 PM UTC
- Resolved
- Jul 06, 2026, 07:00 PM UTC
- Duration
- 1h 48m
Affected: Firebox Configuration:::AMERFirebox Configuration:::EMEAFirebox Configuration:::APAC
Timeline · 5 updates
-
investigating Jul 06, 2026, 05:12 PM UTC
We're investigating errors when viewing firmware upgrade details. Once we determine the impact and scale of these errors, we'll post our next update in 30 minutes, if not sooner.
-
investigating Jul 06, 2026, 05:41 PM UTC
We continue to investigate errors when viewing firmware upgrade details and will post our next update in 30 minutes if not sooner.
-
identified Jul 06, 2026, 06:04 PM UTC
We continue to work on errors when viewing firmware upgrade details and have identified the issue. 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 30 minutes, if not sooner.
-
monitoring Jul 06, 2026, 06:31 PM UTC
Our systems show errors when viewing firmware upgrade details are returning to normal and we're monitoring to ensure system stability. We'll post our next update in 30 minutes, if not sooner.
-
resolved Jul 06, 2026, 07:00 PM UTC
We are no longer experiencing errors when viewing firmware upgrade details and this event is now resolved. The system is operating normally at this time.
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2026, 01:12 PM UTC
- Resolved
- Jul 02, 2026, 03:12 PM UTC
- Duration
- 1h 59m
Affected: Incident Persistence:::EMEAIncident Persistence:::AMERIncident Persistence:::APACEvent Collection:::EMEAEvent Collection:::AMEREvent Collection:::APAC
Timeline · 5 updates
-
investigating Jul 02, 2026, 01:12 PM UTC
We're investigating alerts on ThreatSync incident service. Once we determine the impact and scale of these errors we'll post our next update in 30 minutes, if not sooner.
-
identified Jul 02, 2026, 01:23 PM UTC
We continue to work on ThreatSync incidents service and have identified the issue. 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 60 minutes, if not sooner.
-
identified Jul 02, 2026, 02:18 PM UTC
We are still working hard to resolve this event. Please check back at 30 minutes for updates. Thanks for your patience.
-
monitoring Jul 02, 2026, 02:49 PM UTC
Our systems show alerts on ThreatSync incidents service are returning to normal and we're monitoring to ensure system stability. We'll post our next update in 30 minutes, if not sooner.
-
resolved Jul 02, 2026, 03:12 PM UTC
We are no longer experiencing alerts on ThreatSync incidents service and this incident is now resolved. The service is operating normally at this time.
Read the full incident report →
- Detected by Pingoru
- Jun 26, 2026, 10:20 AM UTC
- Resolved
- Jun 26, 2026, 11:21 AM UTC
- Duration
- 1h 1m
Affected: Account Administration:::EMEAOperator Administration:::EMEA
Timeline · 4 updates
-
investigating Jun 26, 2026, 10:20 AM UTC
We're investigating errors in retrieving account details. Once we determine the impact and scale of these errors we'll post our next update in 30 minutes, if not sooner.
-
identified Jun 26, 2026, 10:30 AM UTC
The team has identified the issue impacting account and operator administration in the WatchGuard Cloud console and is actively working to restore normal operations. We apologize for any inconvenience this may be causing you or your customers. We will provide the next update in 30 minutes, if not sooner.
-
monitoring Jun 26, 2026, 10:45 AM UTC
The issue has been resolved by our team, and account and operator administration services are returning to normal operations. We are continuing to monitor the system to ensure stability. We apologize for the inconvenience and any impact this may have had on you or your customers.
-
resolved Jun 26, 2026, 11:21 AM UTC
We are no longer experiencing errors with the account and operator administration and this incident is now resolved. Again, we apologize for any impact this may have had on you or your customers.
Read the full incident report →
- Detected by Pingoru
- Jun 19, 2026, 12:50 PM UTC
- Resolved
- Jun 19, 2026, 06:04 PM UTC
- Duration
- 5h 14m
Affected: Account Administration:::AMERAccount Administration:::EMEAAccount Administration:::APAC
Timeline · 5 updates
-
identified Jun 19, 2026, 12:50 PM UTC
We have identified an issue affecting administration managed access in WatchGuard Cloud when some users try to enable support access. The team is already working on a fix, we will post our next update in 1 hour or earlier.
-
identified Jun 19, 2026, 01:52 PM UTC
We continue to work on resolving the event affecting administration managed access in WatchGuard Cloud. Our team is working to restore normal operations and we apologize for the impact this event has caused. We'll post our next update in 1 hour If not sooner.
-
identified Jun 19, 2026, 02:56 PM UTC
We are still working hard to resolve this event. Please check back at 18:00 UTC for updates. Thanks for your patience.
-
monitoring Jun 19, 2026, 05:35 PM UTC
A fix has been deployed to address the issue affecting the administration of managed access in WatchGuard Cloud when trying to enable support access. We are monitoring to ensure system stability. We'll post our next update in 30 minutes if not sooner.
-
resolved Jun 19, 2026, 06:04 PM UTC
We are no longer experiencing errors while enabling managed access in WatchGuard Cloud. This incident is now resolved. The system is operating normally at this time.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 01:55 PM UTC
- Resolved
- Jun 11, 2026, 03:10 AM UTC
- Duration
- 13h 15m
Affected: Administration:::GLOBEAdministration:::AMERAdministration:::EMEAAdministration:::APACConsole:::GLOBEConsole:::AMERConsole:::EMEAConsole:::APAC
Timeline · 7 updates
Read the full incident report →