Is FortiSASE down?

We are investigating an intermittent network disruption impacting certain routes into the Columbus, Ohio Public Cloud region. Our engineering team has engaged and is actively working to identify the cause. If you have questions about this incident, please contact FortiCare Support and reference ticket #542406.

The cloud provider has confirmed a network incident affecting this region. Remediation is underway on their end, but the PoP has remained stable in the interim. We will continue to monitor. If you have questions about this incident, please contact FortiCare Support and reference ticket #542406.

This incident has been resolved.

We are investigating an issue affecting customers connected to the Dallas and Plano PoPs where domains with an established rating in FortiGuard may be incorrectly classified as "Unrated" or "Newly Observed Domain" during category lookups. Domains that display a valid web category rating on fortiguard.com are being returned with an incorrect classification, which may result in unexpected policy enforcement behavior for affected traffic. This is being escalated to the FortiGuard team for review. We will provide updates as they become available. If you have questions regarding this incident, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #542286.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating a service disruption affecting the San José, California PoP. This location is no longer operational and customers routing traffic through this location may experience connectivity issues. Our engineering team is actively working on the issue and already reached out relevant team, thanks to let us provide further updates as soon as more information becomes available.

Connectivity to the San Jose infrastructure has been fully restored and all services are now operating normally. We will continue to monitor the situation to ensure stability.

This incident has been resolved.

We are currently observing partial degradation of connectivity to Endpoint Management systems across multiple regions, with the most significant impact on West Coast US. Customers whose EMS is hosted in these regions may experience intermittent connectivity. We apologize for any inconvenience this may cause and will provide updates as we make progress toward resolution. If you have any questions regarding this incident, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #529190.

We are continuing to investigate this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

An issue on Airtel's network is impacting inbound connectivity from many North American networks to our India PoPs. Both Fortinet-operated and cloud-hosted PoPs across India are affected. SIA and SPA traffic to these PoPs may experience elevated latency and intermittent packet loss (upward of 30 to 40 percent). The issue is isolated to traffic traversing Airtel's network. Other paths into the region, as well as traffic within India, appear unaffected. Mitigation in progress: We proactively withdrew our eBGP advertisements to Airtel in Pune to steer traffic onto healthy paths, and we are applying the same change in Bangalore. External cloud providers have also been notified so they can adjust routing on their side as needed. Note that the observed behavior is occurring well outside our network, on provider-managed paths we do not control. If you have any questions regarding this incident, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #528142.

We completed the withdrawal of eBGP advertisements to Airtel in Bangalore, steering traffic onto healthy paths, and have continued monitoring since. Results have improved significantly, though some upstream paths through Airtel may still see impact in certain cases. Overall impact is reduced, and traffic will remain re-routed on Fortinet PoPs for the time being. The provider has reported a fiber cut impacting this international connectivity and is working with local authorities on a resolution. No provider fix is available yet for the affected paths. The observed behavior is occurring outside our network, on provider-managed paths we do not control, and the impacted external cloud provider has not yet provided any update on routing around the issue. We will continue monitoring and share further updates as the situation develops.

The provider has confirmed that the affected path is now fully recovered. As a precaution, Airtel remains withdrawn from our eBGP peering for the India PoPs while we validate stability. We plan to reintroduce Airtel on July 1 with AS-path prepending applied, which will allow the path to carry traffic in a limited capacity while we continue to monitor performance. We are marking this incident as resolved. The remaining actions, including reintroducing Airtel and later fully restoring it as a standard provider in our routing blend, are routine and should not introduce any further customer impact.