Cato Networks Outage History

Cato Networks degraded · 1 active incident View live status →

Cato Networks had 8 outages in the last 2 years totaling 151h 35m of downtime — averaging 0.3 incidents per month.

There were 8 Cato Networks outages since October 7, 2026 totaling 151h 35m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.catonetworks.com

Minor October 20, 2026

PoP Infrastructure - Services degradation issue

Detected by Pingoru
Oct 20, 2026, 10:30 PM UTC
Resolved
Oct 20, 2026, 10:36 PM UTC
Duration
6m
Affected: Manila, Philippines
Timeline · 4 updates
  1. identified Oct 20, 2026, 10:30 PM UTC

    We identified issues in the Cato Cloud related to the PoP infrastructure. Users may experience network performance and connectivity issues. Our engineers are working to restore the services. We will update you when the issue is resolved, or we have more information. Questions? Please contact our Support team. We appreciate your patience and apologize for any related inconvenience. [Ref: ENG-220815]

  2. identified Oct 20, 2026, 10:32 PM UTC

    Our investigation indicates that the issue began at approximately 21:50 UTC on 20-OCT-2026. The investigation is still ongoing. We will provide updates as they become available. We appreciate your patience. Questions? Please contact our Support team. [Ref: ENG-221116]

  3. monitoring Oct 20, 2026, 10:34 PM UTC

    We implemented the fix, and are monitoring the situation to make sure that it is 100% resolved. Updates will be forthcoming. We appreciate your patience. Questions? Please contact our Support team. [Ref: ENG-221116]

  4. resolved Oct 20, 2026, 10:36 PM UTC

    The service is fully operational. If you have any further questions, please contact our Support team. We appreciate your patience and apologize for any related inconvenience. [Ref: ENG-221116]

Read the full incident report →

Minor October 19, 2026

PoP Infrastructure - Services degradation due to carrier issues

Detected by Pingoru
Oct 19, 2026, 12:54 PM UTC
Resolved
Oct 19, 2026, 07:24 PM UTC
Duration
6h 30m
Affected: Sao Paulo, Brazil
Timeline · 4 updates
  1. identified Oct 19, 2026, 12:54 PM UTC

    We identified that an upstream carrier is experiencing issues, which may impact users with packet loss, high latency, or connectivity issues. Our engineers are working with the carrier to resolve the issues ASAP. We will update you when the issue is resolved, or we have more information. Questions? Please contact our Support team. We appreciate your patience and apologize for any related inconvenience.

  2. identified Oct 19, 2026, 12:57 PM UTC

    Our investigation indicates that the issue began at approximately 11:00 UTC on 19-Oct-2026. The investigation is still ongoing. We will provide updates as they become available. We appreciate your patience. Questions? Please contact our Support team.

  3. monitoring Oct 19, 2026, 03:26 PM UTC

    The issue is now resolved, and we're closely monitoring to ensure everything is stable. Updates will be forthcoming. We appreciate your patience. Questions? Please contact our Support team. [Ref: INCIDNT-10198]

  4. resolved Oct 19, 2026, 07:24 PM UTC

    The service is fully operational. If you have any further questions, please contact our Support team. We appreciate your patience and apologize for any related inconvenience. [Ref: INCIDNT-10198]

Read the full incident report →

Major October 19, 2026

PoP Infrastructure - Services availability issue

Detected by Pingoru
Oct 19, 2026, 10:43 AM UTC
Resolved
Oct 19, 2026, 10:58 AM UTC
Duration
15m
Affected: Santa Clara, California
Timeline · 1 update
  1. investigating Oct 19, 2026, 10:43 AM UTC

    We identified that our services are down due to infrastructure issues. Users may experience network performance and connectivity issues. We are working to fix the issues ASAP. We will update you when the issue is resolved, or we have more information. Questions? Please contact our Support team. We appreciate your patience and apologize for any related inconvenience. *if no impact will be found this post will be deleted retroactively

Read the full incident report →

Minor October 16, 2026

Cato Management Application Incident - Intermittent delays for Analytics data

Detected by Pingoru
Oct 16, 2026, 09:43 AM UTC
Resolved
Oct 16, 2026, 12:40 PM UTC
Duration
2h 57m
Affected: Digital Experience MonitorAnalytics
Timeline · 3 updates
  1. identified Oct 16, 2026, 09:43 AM UTC

    We identified some delays related to Analytics and Monitoring data in the Cato Management Application. There is no impact to your network services. Our team is working to fix the issue as soon as possible. We will update you when the issue is resolved, or we have more information. Questions? Please contact our Support team. We appreciate your patience and apologize for any related inconvenience.

  2. monitoring Oct 16, 2026, 12:09 PM UTC

    The issue is now resolved, and we're closely monitoring to ensure everything is stable. Updates will be forthcoming. We appreciate your patience. Questions? Please contact our Support team. [Ref: INCIDNT-10179]

  3. resolved Oct 16, 2026, 12:40 PM UTC

    The service is fully operational. If you have any further questions, please contact our Support team. We appreciate your patience and apologize for any related inconvenience. [Ref: INCIDNT-10179]

Read the full incident report →

Minor October 15, 2026

PoP Infrastructure - Service Degradation due to Carrier Outage

Detected by Pingoru
Oct 15, 2026, 06:00 PM UTC
Resolved
Oct 16, 2026, 03:30 AM UTC
Duration
9h 30m
Affected: Urumqi, China
Timeline · 3 updates
  1. identified Oct 15, 2026, 06:00 PM UTC

    We have identified an issue with an upstream carrier that may result in packet loss, increased latency, or intermittent connectivity for some users. This issue may also affect the processing of Events and Analytics data for sites connected to the affected PoP. Our engineers are working with the carrier to resolve the issues ASAP. We will update you when the issue is resolved, or we have more information. Questions? Please contact our Support team. We appreciate your patience and apologize for any related inconvenience. [Ref: INCIDNT-10177 ]

  2. monitoring Oct 16, 2026, 01:48 AM UTC

    We observed that connectivity issues are resolved, and we are waiting for the carrier to announce that they completed their repairs. We are continuing to monitor the situation to make sure that it is 100% resolved. We will update you when more information is available. We appreciate your patience. Questions? Please contact our Support team. [Ref: INCIDNT-10177 ]

  3. resolved Oct 16, 2026, 03:30 AM UTC

    Following an extended period of monitoring, we can confirm that connectivity has been fully restored and all services are 100% operational. If you have any further questions, please contact our Support team. We appreciate your patience and apologize for any related inconvenience. [Ref: INCIDNT-10177 ]

Read the full incident report →

Minor October 15, 2026

Cato Management Application Incident - Intermittent Availability Issue

Detected by Pingoru
Oct 15, 2026, 09:44 AM UTC
Resolved
Oct 20, 2026, 05:20 PM UTC
Duration
5d 7h
Affected: Johannesburg, South AfricaTokyo_DC3, JapanOsaka_DC2, JapanTokyo_DC2, JapanOsaka,JapanTokyo_DC4, JapanTokyo, Japan
Timeline · 6 updates
  1. identified Oct 15, 2026, 09:44 AM UTC

    We identified an intermittent issue that impacts access to the Cato Management Application. There is no impact to your network services. Our team is working to fix the issue as soon as possible. If you require assistance or need to report a service problem while we work to restore access, you can reach Cato Support by calling one of the following numbers: USA: +1 505 333 4070 United Kingdom: +44 114 303 3899 Israel: +972 3 720 7171 Singapore: +65 3138 9013 We will update you when the issue is resolved, or we have more information. We appreciate your patience and apologize for any related inconvenience.

  2. resolved Oct 15, 2026, 03:00 PM UTC

    The service is fully operational. If you have any further questions, please contact our Support team. We appreciate your patience and apologize for any related inconvenience. [Ref: INCIDNT-10173]

  3. investigating Oct 20, 2026, 04:30 AM UTC

    We are continuing to investigate the issue and have engaged our Engineering team for further analysis and troubleshooting. We remain focused on identifying the root cause and will provide additional updates as more information becomes available or progress is made toward resolution. We appreciate your patience. Questions? Please contact our Support team. [Ref: INCIDNT-10173]

  4. investigating Oct 20, 2026, 07:55 AM UTC

    We are actively investigating the issue and have involved our Engineering team for further analysis and troubleshooting. We are primarily focused on identifying the root cause, and we will provide updates as new information becomes available or as we progress toward a resolution. We appreciate your patience. Questions? Please contact our Support team. [Ref: INCIDNT-10173]

  5. investigating Oct 20, 2026, 08:20 AM UTC

    Our investigation has identified the source of the issue as a problematic server within our third-party provider's infrastructure, which handles Web Application Firewall (WAF) and DDoS protection services. Our Engineering team is fully engaged and working closely with the provider to evaluate and implement the most effective solution to restore stable access to the Cato Management Application (CMA). Resolving this issue remains our highest priority, and all necessary resources are dedicated to minimizing further disruptions. We will continue to provide updates as progress is made. We appreciate your patience. Questions? Please contact our Support team. [Ref: INCIDNT-10173]

  6. resolved Oct 20, 2026, 05:20 PM UTC

    The service is fully operational. If you have any further questions, please contact our Support team. We appreciate your patience and apologize for any related inconvenience. [Ref: INCIDNT-10173]

Read the full incident report →

Minor October 13, 2026

PoP Infrastructure - Services degradation for non-redundant network setup

Detected by Pingoru
Oct 13, 2026, 12:04 AM UTC
Resolved
Oct 13, 2026, 01:24 AM UTC
Duration
1h 20m
Affected: Amsterdam, The Netherlands
Timeline · 2 updates
  1. identified Oct 13, 2026, 12:04 AM UTC

    We have identified issues in the Cato Cloud related to the PoP infrastructure that are impacting non-redundant configurations. Impacted configurations include egress Network Rules, RPF, and IPSec sites with a single active tunnel (primary connection only). The issue is limited in scope and affects a subset of customers. Redundant configurations remain stable. Our engineers are working to restore the services. We will update you when the issue is resolved, or we have more information. Questions? Please contact our Support team. We appreciate your patience and apologize for any related inconvenience. [Ref: INCIDNT-10149]

  2. resolved Oct 13, 2026, 01:24 AM UTC

    The service is fully operational. If you have any further questions, please contact our Support team. We appreciate your patience and apologize for any related inconvenience. [Ref: INCIDNT-10149]

Read the full incident report →

Minor October 9, 2026

PoP Infrastructure - WAN connectivity degradation issues

Detected by Pingoru
Oct 09, 2026, 06:24 PM UTC
Resolved
Oct 09, 2026, 09:42 PM UTC
Duration
3h 18m
Affected: Mexico City, Mexico
Timeline · 4 updates
  1. investigating Oct 09, 2026, 06:24 PM UTC

    We identified that an upstream carrier is experiencing issues, which may impact users with packet loss, high latency, or connectivity issues. Our engineers are working with the carrier to resolve the issues ASAP. We will update you when the issue is resolved, or we have more information. Questions? Please contact our Support team. We appreciate your patience and apologize for any related inconvenience. Ref: [INCIDNT-10135]

  2. investigating Oct 09, 2026, 07:00 PM UTC

    The carrier is investigating the issue and is working to repair it ASAP. However, the carrier has not provided an ETA for the resolution. We will update you when the issue is resolved, or we have more information. We appreciate your patience. Questions? Please contact our Support team. Ref: [INCIDNT-10135]

  3. monitoring Oct 09, 2026, 09:32 PM UTC

    The issue is now resolved, and we're closely monitoring to ensure everything is stable. Updates will be forthcoming. We appreciate your patience. Questions? Please contact our Support team. Ref: [INCIDNT-10135]

  4. resolved Oct 09, 2026, 09:42 PM UTC

    The service is fully operational. If you have any further questions, please contact our Support team. We appreciate your patience and apologize for any related inconvenience. Ref: [INCIDNT-10135]

Read the full incident report →