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, China (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, Brazil (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, TX, US (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, FL, US (MIA-F3)
Operational
Burnaby, Canada (YVR-F5)
Operational
Bangalore, India (BLR-F2)
Operational
Ashburn, VA, US (IAD-F5)
Operational
Sydney, Australia (SYD-F3)
Operational
Dubai, UAE (DXB-F3)
Operational
Taipei, Taiwan (TPE-F1)
Operational
Ashburn, VA, US (IAD-F2)
Operational
Tokyo, Japan (TYO-F3)
Operational
San Jose, CA, US (SJC-F5)
Operational
Kamloops, Canada (YKA-F1)
Operational
Dubai, UAE (DXB-F4)
Operational
Paris, France (PAR-F5)
Operational
Leeds, United Kingdom (LBA-F1)
Operational
Public Cloud Locations
Operational
Johannesburg, South Africa (JNB-G2)
Operational
Tel Aviv, Israel (TLV-G1)
Operational
Hamina, Finland (HEL-G2)
Operational
Eemshaven, 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
The Dalles, OR, US (PDX-G2)
Operational
Jakarta, Indonesia (JKT-G2)
Operational
Milan, Italy (MIL-G2)
Operational
São 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, United Kingdom (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
Tokyo, Japan (TYO-G2)
Operational
Bangkok, Thailand (BKK-A1)
Operational
Columbus, OH, US (CMH-G2)
Operational
Moncks Corner, SC, 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
Milan, Italy (MIL-O1)
Operational
Frankfurt, Germany (FRA-O1)
Operational
Jeddah, Saudi Arabia (JED-O1)
Operational
Abu Dhabi, UAE (AUH-O1)
Operational
Ashburn, VA, US (IAD-O1)
Operational
Stockholm, Sweden (STO-O1)
Operational
Chicago, IL, US (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
Monterrey, Mexico (MTY-O1)
Operational
Riyadh, Saudi Arabia (RUH-O1)
Operational
KSA Cloud Regions
Operational
Dammam Zone B
Operational
Dammam Zone C
Operational
Riyadh
Operational
Jeddah
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 Endpoint Management - Proactive Maintenance Aug 17, 2026 00:00 - Sep 7, 2026 04:00 UTC
Anticipated Impact:
Endpoint Management connections will reestablish, potentially delaying Telemetry updates up to 5 minutes during a single maintenance window.
What to expect during your maintenance window:
* EMS connectivity may reestablish, briefly affecting Endpoint Management functions including Telemetry.
* Temporary impact may last up to 5 minutes.
Note: This maintenance does not impact overall data flow or network connectivity.
For further details, please see the following document:
https://docs.fortinet.com/document/fortisase/7.4.0/administration-guide/12689/endpoint-management-upgrade
This proactive maintenance will follow the same maintenance window scheduling as tenant upgrades and each customer instance will only be impacted once during this maintenance period, upgrades will occur Monday 00:00 to Friday 23:59 UTC outside of major holidays.
https://docs.fortinet.com/document/fortisase/7.4.0/administration-guide/190872/appendix-e-monthly-maintenance
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #590568.
Posted on Aug 14, 2026 - 16:17 UTC
Endpoint Management connections will reestablish, potentially delaying Telemetry updates up to 5 minutes during a single maintenance window.
What to expect during your maintenance window:
* EMS connectivity may reestablish, briefly affecting Endpoint Management functions including Telemetry.
* Temporary impact may last up to 5 minutes.
Note: This maintenance does not impact overall data flow or network connectivity.
For further details, please see the following document:
https://docs.fortinet.com/document/fortisase/7.4.0/administration-guide/12689/endpoint-management-upgrade
This proactive maintenance will follow the same maintenance window scheduling as tenant upgrades and each customer instance will only be impacted once during this maintenance period, upgrades will occur Monday 00:00 to Friday 23:59 UTC outside of major holidays.
https://docs.fortinet.com/document/fortisase/7.4.0/administration-guide/190872/appendix-e-monthly-maintenance
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #590568.
Posted on Aug 14, 2026 - 16:17 UTC
FortiSASE Proactive Software Maintenance for KSA environment only - release 26.2.2 Aug 17, 2026 18:00 - Aug 18, 2026 00: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.
For FortiSASE-v7.4 release:
For integrating a private AD server without exposing it to the internet, added support for creating an AD connector API key in FortiSASE. This API key is used to configure the FortiClient EMS AD Connector to establish a tunnel with FortiSASE. This feature requires a FortiSASE instance supporting FortiClient 7.4.
Added support for ZTNA UDP traffic forwarding from FortiClient 7.4 endpoints. This feature requires an instance supporting FortiClient 7.4, FortiClient 7.4.1 or later installed on endpoints and the FortiGate ZTNA application gateway to be running FortiOS version 7.6.0 or later.
Added new best practice recommendation to detect a newer Security PoP location with superior performance for the same geographic region and guide the user on how to migrate to the new security PoP.
Support has been added for automatic endpoint vulnerability patching in the Operations > Endpoints > Endpoint details pane.
Added support for Secure Browser SSO domain integration where an email address domain for end users to log into is integrated with Secure Browser to support BYOD use cases without using a deployment script.
Added enhancements to SCIM server support including support for large SCIM user populations, support for on-demand provisioning from Entra ID after initial provisioning, and support for more robust handling of error conditions.
Added support for the optional Local ID type in the IPsec Phase 1 settings for the on-ramp tunnel custom device type for third-party devices that require using an IP address for the local ID type.
A RADIUS server timeout option has been added in Access & authentication > RADIUS when creating or editing a connection.
FortiClient 7.4.7 support has been added for the Linux platform for IPsec and SSL VPN tunneling.
Support has been added for the latest FortiClient version for mobile platforms (Android and iOS).
Added support for the MSI version of the FortiClient Windows installer since it was unavailable for new instances created in FortiSASE-v7.4 from 25.4.b to 26.2.1.a.
The FortiSASE Network Tools page (https://speed.fortisase.com/) supports performing speed tests both on and off FortiSASE tunnels.
Added support for Public Cloud security PoPs: Monterrey (Mexico).
Added support for Fortinet security PoPs: Taipei (Taiwan).
Updated support for Fortinet security PoPs: Off-shore Dubai (United Arab Emirates).
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 #590598.
Posted on Aug 10, 2026 - 20:19 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.
For FortiSASE-v7.4 release:
For integrating a private AD server without exposing it to the internet, added support for creating an AD connector API key in FortiSASE. This API key is used to configure the FortiClient EMS AD Connector to establish a tunnel with FortiSASE. This feature requires a FortiSASE instance supporting FortiClient 7.4.
Added support for ZTNA UDP traffic forwarding from FortiClient 7.4 endpoints. This feature requires an instance supporting FortiClient 7.4, FortiClient 7.4.1 or later installed on endpoints and the FortiGate ZTNA application gateway to be running FortiOS version 7.6.0 or later.
Added new best practice recommendation to detect a newer Security PoP location with superior performance for the same geographic region and guide the user on how to migrate to the new security PoP.
Support has been added for automatic endpoint vulnerability patching in the Operations > Endpoints > Endpoint details pane.
Added support for Secure Browser SSO domain integration where an email address domain for end users to log into is integrated with Secure Browser to support BYOD use cases without using a deployment script.
Added enhancements to SCIM server support including support for large SCIM user populations, support for on-demand provisioning from Entra ID after initial provisioning, and support for more robust handling of error conditions.
Added support for the optional Local ID type in the IPsec Phase 1 settings for the on-ramp tunnel custom device type for third-party devices that require using an IP address for the local ID type.
A RADIUS server timeout option has been added in Access & authentication > RADIUS when creating or editing a connection.
FortiClient 7.4.7 support has been added for the Linux platform for IPsec and SSL VPN tunneling.
Support has been added for the latest FortiClient version for mobile platforms (Android and iOS).
Added support for the MSI version of the FortiClient Windows installer since it was unavailable for new instances created in FortiSASE-v7.4 from 25.4.b to 26.2.1.a.
The FortiSASE Network Tools page (https://speed.fortisase.com/) supports performing speed tests both on and off FortiSASE tunnels.
Added support for Public Cloud security PoPs: Monterrey (Mexico).
Added support for Fortinet security PoPs: Taipei (Taiwan).
Updated support for Fortinet security PoPs: Off-shore Dubai (United Arab Emirates).
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 #590598.
Posted on Aug 10, 2026 - 20:19 UTC
FortiSASE Proactive Software Maintenance - FortiSASE release 26.2.2.a [Hotfix] Aug 17, 2026 18:00-19:00 UTC
Anticipated Impact: No expected impact
Our Operations team will be performing multiple proactive Software updates on the backend that powers FortiSASE. There is no expected impact.
For FortiSASE-v7.4 release:
For new and existing instances already on FortiClient 7.4.7, support will be added for FortiClient 7.4.8 for FortiSASE desktop users. For new tenants it will be available immediately and for existing instances it will be added successively throughout the week, starting on Monday, August 17th and ending on Friday August, 21st.
In Endpoint management > Configuration, the All traffic option for the Bypass FortiSASE field can be enabled and configured. When enabled, all traffic will bypass the FortiSASE Cloud Security tunnel except for defined subnets. This feature requires endpoints running FortiClient 7.4.8 or later.
Support has been added for recurring Digital Experience Monitoring traceroutes that collect metrics between the endpoint and security PoP every five minutes. Traceroute information is retained for 14 days. This feature requires endpoints running FortiClient 7.4.8 or later.
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #591801.
Posted on Aug 14, 2026 - 22:44 UTC
Our Operations team will be performing multiple proactive Software updates on the backend that powers FortiSASE. There is no expected impact.
For FortiSASE-v7.4 release:
For new and existing instances already on FortiClient 7.4.7, support will be added for FortiClient 7.4.8 for FortiSASE desktop users. For new tenants it will be available immediately and for existing instances it will be added successively throughout the week, starting on Monday, August 17th and ending on Friday August, 21st.
In Endpoint management > Configuration, the All traffic option for the Bypass FortiSASE field can be enabled and configured. When enabled, all traffic will bypass the FortiSASE Cloud Security tunnel except for defined subnets. This feature requires endpoints running FortiClient 7.4.8 or later.
Support has been added for recurring Digital Experience Monitoring traceroutes that collect metrics between the endpoint and security PoP every five minutes. Traceroute information is retained for 14 days. This feature requires endpoints running FortiClient 7.4.8 or later.
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #591801.
Posted on Aug 14, 2026 - 22:44 UTC