All Systems Operational
FortiSASE Network (AS40934)
Operational
Fortinet Cloud Locations
Operational
Ashburn, VA, US (IAD-F1)
Operational
Dallas, TX, US (DFW-F1)
Operational
Dubai, UAE (DXB-F1)
Operational
Frankfurt, Germany (FRA-F1)
Operational
Hong Kong (HKG-F1)
Operational
Komagome, Japan (TYO-F1)
Operational
London, United Kingdom (LON-F1)
Operational
Miami, FL, US (MIA-F1)
Operational
Ottawa, Canada (YOW-F1)
Operational
Paris, France (PAR-F1)
Operational
San Jose, CA, US (SJC-F1)
Operational
Singapore (SIN-F1)
Operational
Sydney, Australia (SYD-F1)
Operational
Tokyo, Japan (TYO-F2)
Operational
Toronto, Canada (YTO-F1)
Operational
Valbonne, France (NCE-F1)
Operational
Vancouver, Canada (YVR-F2)
Operational
Bangalore, India (BLR-F1)
Operational
Frankfurt, Germany (FRA-F2)
Operational
San Jose, CA, US (SJC-F2)
Operational
Pune, India (PNQ-F1)
Operational
London, United Kingdom (LON-F2)
Operational
Paris, France (PAR-F2)
Operational
Singapore (SIN-F2)
Operational
Miami, FL, US (MIA-F2)
Operational
Dallas, TX, US (DFW-F2)
Operational
Istanbul, Turkey (IST-F1)
Operational
Johannesburg, South Africa (JNB-F1)
Operational
Dubai, UAE (DXB-F2)
Operational
San Jose, CA, US (SJC-F3)
Operational
Frankfurt, Germany (FRA-F3)
Operational
Paris, France (PAR-F3)
Operational
Ashburn, VA, US (IAD-F3)
Operational
London, United Kingdom (LON-F3)
Operational
Plano, TX, US (DFW-F3)
Operational
Madrid, Spain (MAD-F1)
Operational
Singapore (SIN-F3)
Operational
Toronto, Canada (YTO-F2)
Operational
Sydney, Australia (SYD-F2)
Operational
Paris, France (PAR-F4)
Operational
Frankfurt, Germany (FRA-F4)
Operational
São Paulo (GRU-F1)
Operational
Vancouver, Canada (YVR-F3)
Operational
San Jose, CA, US (SJC-F4)
Operational
Burnaby, Canada (YVR-F4)
Operational
Ashburn, VA, US (IAD-F4)
Operational
Plano, Texas USA (DFW-F4)
Operational
Madrid, Spain (MAD-F2)
Operational
Komagome, Japan (TYO-F4)
Operational
Auckland, New Zealand (AKL-F1)
Operational
London, United Kingdom (LON-F4)
Operational
Frankfurt, Germany (FRA-F5)
Operational
Toronto, Canada (YTO-F3)
Operational
Singapore (SIN-F4)
Operational
Miami (MIA-F3)
Operational
Burnaby (YVR-F5)
Operational
Bangalore, India (BLR-F2)
Operational
Ashburn, VA, US (IAD-F5)
Operational
Sydney, Australia (SYD-F3)
Operational
Public Cloud Locations
Operational
Johannesburg, South Africa (JNB-G2)
Operational
Milan, Italy (MIL-G1)
Operational
Tel Aviv, Israel (TLV-G1)
Operational
Hamina, Finland (HEL-G2)
Operational
Amsterdam, Netherlands (AMS-G2)
Operational
Tel Aviv, Israel (TLV-G2)
Operational
Madrid, Spain (MAD-G2)
Operational
Melbourne, Australia (MEL-G2)
Operational
Santiago, Chile (SCL-G2)
Operational
Seoul, South Korea (SEL-G2)
Operational
Doha, Qatar (DOH-G2)
Operational
Ashburn, VA, US (IAD-G2)
Operational
Portland, OR, US (PDX-G2)
Operational
Jakarta, Indonesia (JKT-G2)
Operational
Milan, Italy (MIL-G2)
Operational
Sao Paulo, Brazil (SAO-G2)
Operational
Mumbai, India (BOM-G2)
Operational
Las Vegas, NV, US (LAS-G2)
Operational
Dammam, Saudi Arabia (DMM-G2)
Operational
Taipei, Taiwan (TPE-G2)
Operational
Osaka, Japan (OSA-G2)
Operational
Hong Kong, China (HKG-G2)
Operational
Dallas, TX, US (DFW-G2)
Operational
Sydney, Australia (SYD-G2)
Operational
Querétaro, Mexico (QRO-G2)
Operational
Dublin, Ireland (DUB-A1)
Operational
Perth, Australia (PER-A1)
Operational
Auckland, New Zealand (AKL-A1)
Operational
Delhi, India (DEL-G2)
Operational
Chicago, IL, US (ORD-A1)
Operational
Zurich, Switzerland (ZRH-G2)
Operational
Warsaw, Poland (WAW-G2)
Operational
Buenos Aires , Argentina (BUE-A1)
Operational
St. Ghislain, Belgium (BRU-G2)
Operational
Lima, Peru (LIM-A1)
Operational
London, UK (LON-G2)
Operational
Manila, Philippines (MNL-A1)
Operational
Toronto, Canada (YTO-G2)
Operational
Paris, France (PAR-G2)
Operational
Frankfurt, Germany (FRA-G2)
Operational
Singapore (SIN-G2)
Operational
Miami, FL, US (MIA-A1)
Operational
Montreal, Canada (YMQ-G2)
Operational
Dubai, UAE (DXB-A1)
Operational
Tokyo, Japan (TYO-G2)
Operational
Bangkok, Thailand (BKK-A1)
Operational
Columbus, Ohio, USA (cmh-g2)
Operational
South Carolina ,US (CHS-G2)
Operational
Cyberjaya, Malaysia (KUL-A1)
Operational
Bogotá, Colombia (bog-o1)
Operational
Vinhedo, Brazil (vcp-o1)
Operational
Paris, France (par-o1)
Operational
Mumbai, India (BOM-O1)
Operational
Sydney, Australia (SYD-O1)
Operational
London, United Kingdom (LON-O1)
Operational
Muscat, Oman (MCT-A1)
Operational
Milan, Italy (MIL-O1)
Operational
Frankfurt, Germany (FRA-O1)
Operational
Jeddah, Saudi Arabia (JED-O1)
Operational
Abu Dhabi, UAE (AUH-O1)
Operational
Ashburn, Virginia (IAD-O1)
Operational
Stockholm, Sweden (STO-O1)
Operational
Chicago, Illinois (ORD-O1)
Operational
Osaka, Japan (OSA-O1)
Operational
Montreal, Canada (YMQ-O1)
Operational
Melbourne, Australia (MEL-O1)
Operational
Amsterdam, Netherlands (AMS-O1)
Operational
Santiago, Chile (SCL-O1)
Operational
Dubai, UAE (DXB-O1)
Operational
FortiSASE Services
Operational
FortiSASE Portal
Operational
Endpoint Management
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
FortiSASE Proactive Cloud Computing Services Maintenance Jun 15, 2026 00:00-02:00 UTC
The local operations team will be performing proactive maintenance on cloud computing services. There is a potential for service disruptions and traffic to be re-routed to other PoPs during the window.
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #511917.
Posted on Jun 12, 2026 - 23:20 UTC
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #511917.
Posted on Jun 12, 2026 - 23:20 UTC
FortiSASE Proactive Software Maintenance - FortiSASE release 26.2.1 Jun 16, 2026 00:00 - Jun 19, 2026 08:00 UTC
Anticipated Impact: Potential for short interruption of customer instances and configuration portal during the window.
The Operations team will be installing a rolling software update. There is potential for short connectivity impact (approximately ~1-2 minutes) for each customer instance and the configuration portal while these components are updated. No other impact on service delivery is expected.
Tenant upgrades to 26.2.1 will be processed Tuesday, June 16th through Thursday, June 18th. Upgrades will follow your assigned maintenance window, consistent with prior scheduled maintenances. Customers who have configured a preferred maintenance window in the FortiSASE portal will be upgraded during their selected hours. For details on maintenance window scheduling, see:
https://docs.fortinet.com/document/fortisase/latest/administration-guide/190872/appendix-e-monthly-maintenance
For Feature release:
Integrated FortiCASB-SSPM basic cloud access security broker (CASB) management and advanced SaaS security posture management (SSPM) into FortiSASE for secure SaaS access. A FortiSASE SSPM Protection add-on subscription is required to integrate with several SaaS applications via connectors and to access advanced SSPM features.
Granular control of pre-logon tunnels has been implemented through Secure Private Access (SPA) and Secure Internet Access (SIA) policy management.
Added support for LDAP user authentication with IPsec agent tunnels for both Windows and macOS using the EAP for LDAP authentication setting. This setting is only supported on instances supporting FortiClient 7.4.
Security PoPs can be created, disabled/enabled, decommissioned, and migrated in the Operations > Infrastructure page.
A FortiClient 7.4.7 ARM installer for Windows is available for endpoint onboarding.
In Endpoint management > Endpoint profiles, the On connect script and On disconnect script fields allow the entry of Windows and macOS scripts that will trigger actions when connecting to or disconnecting from Secure Internet Access (SIA), IPsec, or SSL tunnels.
The Security PoP icons and naming convention have been updated to the format City, State (Country) when provisioning a FortiSASE instance and in Operations > Infrastructure. When selecting an entry, hover over the Security PoP name to see more details.
Added support for bring your own device (BYOD) enrollment to a mobile device management (MDM) platform used for installing FortiClient and automatically provisioning a ZTNA client certificate to a device. Currently, only iOS mobile devices are supported with the Intune and JAMF platforms.
When FortiPAM integration is enabled, added support for adding the FortiPAM agent to the FortiClient installer available on the FortiSASE portal. Also, when FortiPAM integration is disabled in FortiSASE, added support for removing the FortiPAM agent from the FortiClient installer and for removing the FortiPAM browser extension.
Improved usability of the Connection tab in an endpoint profile to clearly indicate that local LAN access options apply when connected to a tunnel and that the network lockdown option applies when not connected to a tunnel.
Added option for administrators to override global FortiSASE Cloud Security Tunnel encapsulation to IPsec over TCP via endpoint profile. This allows for IPsec remote user connectivity in cases when Auto option for FortiSASE Cloud Security Tunnel encapsulation is not working since initial IKE negotiation over UDP works fine but ISP blocks UDP ports 500/4500 so fail back to TCP never occurs.
For new instances or existing instances provisioned in 25.4.c Feature or later supporting FortiClient 7.4, added support for the Show Vulnerability Popup toggle that allows administrators to control whether a vulnerability scan summary popup is shown when a scan finds vulnerabilities on a given endpoint.
Updated support for Fortinet security PoPs: Burnaby - Canada.
For Mature release:
The Security PoP icons and naming convention have been updated to the format City, State (Country) when provisioning a FortiSASE instance. When selecting an entry, hover over the Security PoP name to see more details.
Updated support for Fortinet security PoPs: Burnaby - Canada.
Mature to Feature migrations: For selected customer Mature instances, migration to Feature is being incrementally deployed. These customers will receive a notification in the FortiSASE portal in advance. If no action is taken by the week of July 20, 2026, remaining Mature instances will be automatically migrated during a maintenance window to be scheduled shortly thereafter. For details on migrating earlier, see the Mature Admin Guide, specifically, the FAQs > Mature to Feature migration topic or the System > Software audit & version > New major features available topic.
For further information on what's new: https://docs.fortinet.com/document/fortisase/latest/release-notes/661728/whats-new
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #505126.
Posted on Jun 11, 2026 - 20:14 UTC
The Operations team will be installing a rolling software update. There is potential for short connectivity impact (approximately ~1-2 minutes) for each customer instance and the configuration portal while these components are updated. No other impact on service delivery is expected.
Tenant upgrades to 26.2.1 will be processed Tuesday, June 16th through Thursday, June 18th. Upgrades will follow your assigned maintenance window, consistent with prior scheduled maintenances. Customers who have configured a preferred maintenance window in the FortiSASE portal will be upgraded during their selected hours. For details on maintenance window scheduling, see:
https://docs.fortinet.com/document/fortisase/latest/administration-guide/190872/appendix-e-monthly-maintenance
For Feature release:
Integrated FortiCASB-SSPM basic cloud access security broker (CASB) management and advanced SaaS security posture management (SSPM) into FortiSASE for secure SaaS access. A FortiSASE SSPM Protection add-on subscription is required to integrate with several SaaS applications via connectors and to access advanced SSPM features.
Granular control of pre-logon tunnels has been implemented through Secure Private Access (SPA) and Secure Internet Access (SIA) policy management.
Added support for LDAP user authentication with IPsec agent tunnels for both Windows and macOS using the EAP for LDAP authentication setting. This setting is only supported on instances supporting FortiClient 7.4.
Security PoPs can be created, disabled/enabled, decommissioned, and migrated in the Operations > Infrastructure page.
A FortiClient 7.4.7 ARM installer for Windows is available for endpoint onboarding.
In Endpoint management > Endpoint profiles, the On connect script and On disconnect script fields allow the entry of Windows and macOS scripts that will trigger actions when connecting to or disconnecting from Secure Internet Access (SIA), IPsec, or SSL tunnels.
The Security PoP icons and naming convention have been updated to the format City, State (Country) when provisioning a FortiSASE instance and in Operations > Infrastructure. When selecting an entry, hover over the Security PoP name to see more details.
Added support for bring your own device (BYOD) enrollment to a mobile device management (MDM) platform used for installing FortiClient and automatically provisioning a ZTNA client certificate to a device. Currently, only iOS mobile devices are supported with the Intune and JAMF platforms.
When FortiPAM integration is enabled, added support for adding the FortiPAM agent to the FortiClient installer available on the FortiSASE portal. Also, when FortiPAM integration is disabled in FortiSASE, added support for removing the FortiPAM agent from the FortiClient installer and for removing the FortiPAM browser extension.
Improved usability of the Connection tab in an endpoint profile to clearly indicate that local LAN access options apply when connected to a tunnel and that the network lockdown option applies when not connected to a tunnel.
Added option for administrators to override global FortiSASE Cloud Security Tunnel encapsulation to IPsec over TCP via endpoint profile. This allows for IPsec remote user connectivity in cases when Auto option for FortiSASE Cloud Security Tunnel encapsulation is not working since initial IKE negotiation over UDP works fine but ISP blocks UDP ports 500/4500 so fail back to TCP never occurs.
For new instances or existing instances provisioned in 25.4.c Feature or later supporting FortiClient 7.4, added support for the Show Vulnerability Popup toggle that allows administrators to control whether a vulnerability scan summary popup is shown when a scan finds vulnerabilities on a given endpoint.
Updated support for Fortinet security PoPs: Burnaby - Canada.
For Mature release:
The Security PoP icons and naming convention have been updated to the format City, State (Country) when provisioning a FortiSASE instance. When selecting an entry, hover over the Security PoP name to see more details.
Updated support for Fortinet security PoPs: Burnaby - Canada.
Mature to Feature migrations: For selected customer Mature instances, migration to Feature is being incrementally deployed. These customers will receive a notification in the FortiSASE portal in advance. If no action is taken by the week of July 20, 2026, remaining Mature instances will be automatically migrated during a maintenance window to be scheduled shortly thereafter. For details on migrating earlier, see the Mature Admin Guide, specifically, the FAQs > Mature to Feature migration topic or the System > Software audit & version > New major features available topic.
For further information on what's new: https://docs.fortinet.com/document/fortisase/latest/release-notes/661728/whats-new
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #505126.
Posted on Jun 11, 2026 - 20:14 UTC
FortiSASE Proactive Cloud Computing Services Maintenance Jun 18, 2026 18:00-19:00 UTC
FortiSASE Proactive Cloud Computing Services Maintenance
The local operations team will be performing proactive maintenance on cloud computing services. There is a potential for service disruptions and traffic to be re-routed to other PoPs during the window.
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #511704.
Posted on Jun 12, 2026 - 20:30 UTC
The local operations team will be performing proactive maintenance on cloud computing services. There is a potential for service disruptions and traffic to be re-routed to other PoPs during the window.
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #511704.
Posted on Jun 12, 2026 - 20:30 UTC