FortiSASE incident

Upstream ISP Connectivity Incident

Major Resolved View vendor source →

FortiSASE experienced a major incident on November 24, 2025 affecting Ashburn, VA, US (IAD-F1) and Endpoint Management and 1 more component, lasting 3h 52m. The incident has been resolved; the full update timeline is below.

Started
Nov 24, 2025, 04:36 PM UTC
Resolved
Nov 24, 2025, 08:29 PM UTC
Duration
3h 52m
Detected by Pingoru
Nov 24, 2025, 04:36 PM UTC

Affected components

Ashburn, VA, US (IAD-F1)Endpoint ManagementDubai, UAE (DXB-F1)San Jose, CA, US (SJC-F1)Bangalore, India (BLR-F1)San Jose, CA, US (SJC-F2)San Jose, CA, US (SJC-F3)Ashburn, VA, US (IAD-F3)

Update timeline

  1. identified Nov 24, 2025, 04:36 PM UTC

    We have identified an upstream ISP connectivity issue for BLR-F1 (Bangalore) & DXB-F1 (Dubai). We are actively working with our external service providers to fully restore connectivity. If you have any questions regarding this incident, please contact FortiCare Support ( https://www.fortinet.com/support/contact ) and reference FortiSASE Operations ticket #413421.

  2. identified Nov 24, 2025, 05:51 PM UTC

    We are continuing to work on a fix for this issue.

  3. identified Nov 24, 2025, 05:51 PM UTC

    Additional impact has been observed for Endpoint Management traffic in Bangalore and Dubai, as well as management traffic for San Jose and Ashburn PoPs. This incident should not have an impact on customer data flow, but may result in degradation/inability to access the SASE portal for customers in these locations.

  4. identified Nov 24, 2025, 05:51 PM UTC

    We are continuing to work on a fix for this issue.

  5. identified Nov 24, 2025, 05:53 PM UTC

    We are continuing to work on a fix for this issue.

  6. identified Nov 24, 2025, 05:55 PM UTC

    We are continuing to work on a fix for this issue.

  7. monitoring Nov 24, 2025, 06:15 PM UTC

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

  8. resolved Nov 24, 2025, 08:29 PM UTC

    Connectivity through the upstream provider has remained stable. This incident is considered resolved.