In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 14, 2026 - 17:00 UTC
Sep 14, 2026 - 17:00 UTC
Scheduled - Anticipated Impact: FortiSASE UI might be inaccessible for up to 5 minutes
Our Operations team will be performing multiple proactive Software updates on the backend that powers FortiSASE. During the scheduled maintenance window, the FortiSASE UI might be inaccessible for up to 5 minutes. There is no impact to data flow.
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #603130.
Sep 14, 2026 17:00-21:00 UTC
Our Operations team will be performing multiple proactive Software updates on the backend that powers FortiSASE. During the scheduled maintenance window, the FortiSASE UI might be inaccessible for up to 5 minutes. There is no impact to data flow.
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #603130.
Sep 14, 2026 17:00-21:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 14, 2026 - 00:00 UTC
Sep 14, 2026 - 00:00 UTC
Scheduled - 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.3.1 will be processed Monday, September 14th through Friday, September 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 FortiSASE-v7.4 release:
SSL to IPsec transition mode has been enabled for existing SSL instances prior to FortiSASE 26.3.1, allowing side-by-side SSL and IPsec tunnel testing before the eventual one-way transition to IPsec remote user connectivity.
Added support for importing a SAML IdP XML metadata file to auto-fill configuration on the Access and authentication > Authentication Sources > SSO page.
The Global PoP addon license is available for Advanced subscription instances, allowing deployment of an unlimited number of security PoPs selected from supported Advanced subscription locations.
Added support to register or exclude physical adapter and tunnel IP addresses on the DNS server for Active Directory Windows endpoints.
Enhancements have been made to Endpoint management > Configuration > Endpoint profile control.
The endpoint Authentication timeout value has been updated to range from 120 to 172,800 seconds in Endpoint management > Configuration > Global.
Added support for manually quarantining managed FortiClient endpoints to block network access during administrator audit or investigation.
Added support for FortiGate access keys, allowing a ZTNA application gateway FortiGate to connect to a FortiSASE instance in a different FortiCloud account for agent-based ZTNA in MSSP deployments.
Added support for configuring the public IP a security PoP uses for source NAT on outgoing remote user traffic, based on destination address type.
Added support for configuring on-ramp security PoP IP anchoring settings from Network > IP management > Public IP.
Added support for configuring multiple FortiAuthenticator IP addresses, FQDNs, or hostnames in the FSSO tab of an endpoint profile.
The FortiSASE portal session timeout value can be configured in System > Administration, with a range of 5 to 480 minutes.
Added support for administrators to back up and restore selected user configuration settings (max 10 stored). This is a select availability feature not enabled by default. Contact FortiCare Support to enable.
Security PoP region IDs have been updated to denote location code and PoP type, for example the Ashburn, Virginia Fortinet Cloud PoP displays as IAD-F5.
Added analytics support for Public Cloud security PoPs: Jeddah (Saudi Arabia) and Santiago (Chile).
Added support for the Fortinet security PoP: Leeds (United Kingdom).
Updated support for Fortinet security PoPs: Paris (France), San Jose, California (United States).
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 #603130.
Sep 14, 2026 00:00 - Sep 19, 2026 04:00 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.3.1 will be processed Monday, September 14th through Friday, September 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 FortiSASE-v7.4 release:
SSL to IPsec transition mode has been enabled for existing SSL instances prior to FortiSASE 26.3.1, allowing side-by-side SSL and IPsec tunnel testing before the eventual one-way transition to IPsec remote user connectivity.
Added support for importing a SAML IdP XML metadata file to auto-fill configuration on the Access and authentication > Authentication Sources > SSO page.
The Global PoP addon license is available for Advanced subscription instances, allowing deployment of an unlimited number of security PoPs selected from supported Advanced subscription locations.
Added support to register or exclude physical adapter and tunnel IP addresses on the DNS server for Active Directory Windows endpoints.
Enhancements have been made to Endpoint management > Configuration > Endpoint profile control.
The endpoint Authentication timeout value has been updated to range from 120 to 172,800 seconds in Endpoint management > Configuration > Global.
Added support for manually quarantining managed FortiClient endpoints to block network access during administrator audit or investigation.
Added support for FortiGate access keys, allowing a ZTNA application gateway FortiGate to connect to a FortiSASE instance in a different FortiCloud account for agent-based ZTNA in MSSP deployments.
Added support for configuring the public IP a security PoP uses for source NAT on outgoing remote user traffic, based on destination address type.
Added support for configuring on-ramp security PoP IP anchoring settings from Network > IP management > Public IP.
Added support for configuring multiple FortiAuthenticator IP addresses, FQDNs, or hostnames in the FSSO tab of an endpoint profile.
The FortiSASE portal session timeout value can be configured in System > Administration, with a range of 5 to 480 minutes.
Added support for administrators to back up and restore selected user configuration settings (max 10 stored). This is a select availability feature not enabled by default. Contact FortiCare Support to enable.
Security PoP region IDs have been updated to denote location code and PoP type, for example the Ashburn, Virginia Fortinet Cloud PoP displays as IAD-F5.
Added analytics support for Public Cloud security PoPs: Jeddah (Saudi Arabia) and Santiago (Chile).
Added support for the Fortinet security PoP: Leeds (United Kingdom).
Updated support for Fortinet security PoPs: Paris (France), San Jose, California (United States).
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 #603130.
Sep 14, 2026 00:00 - Sep 19, 2026 04:00 UTC
FortiSASE Network (AS40934)
Operational
Fortinet Cloud Locations
Under Maintenance
Ashburn, VA, US (IAD-F1)
Under Maintenance
Dallas, TX, US (DFW-F1)
Under Maintenance
Dubai, UAE (DXB-F1)
Under Maintenance
Frankfurt, Germany (FRA-F1)
Under Maintenance
Hong Kong, China (HKG-F1)
Under Maintenance
Komagome, Japan (TYO-F1)
Under Maintenance
London, United Kingdom (LON-F1)
Under Maintenance
Miami, FL, US (MIA-F1)
Under Maintenance
Ottawa, Canada (YOW-F1)
Under Maintenance
Paris, France (PAR-F1)
Under Maintenance
San Jose, CA, US (SJC-F1)
Under Maintenance
Singapore (SIN-F1)
Under Maintenance
Sydney, Australia (SYD-F1)
Under Maintenance
Tokyo, Japan (TYO-F2)
Under Maintenance
Toronto, Canada (YTO-F1)
Under Maintenance
Valbonne, France (NCE-F1)
Under Maintenance
Vancouver, Canada (YVR-F2)
Under Maintenance
Bangalore, India (BLR-F1)
Under Maintenance
Frankfurt, Germany (FRA-F2)
Under Maintenance
San Jose, CA, US (SJC-F2)
Under Maintenance
Pune, India (PNQ-F1)
Under Maintenance
London, United Kingdom (LON-F2)
Under Maintenance
Paris, France (PAR-F2)
Under Maintenance
Singapore (SIN-F2)
Under Maintenance
Miami, FL, US (MIA-F2)
Under Maintenance
Dallas, TX, US (DFW-F2)
Under Maintenance
Istanbul, Turkey (IST-F1)
Under Maintenance
Johannesburg, South Africa (JNB-F1)
Under Maintenance
Dubai, UAE (DXB-F2)
Under Maintenance
San Jose, CA, US (SJC-F3)
Under Maintenance
Frankfurt, Germany (FRA-F3)
Under Maintenance
Paris, France (PAR-F3)
Under Maintenance
Ashburn, VA, US (IAD-F3)
Under Maintenance
London, United Kingdom (LON-F3)
Under Maintenance
Plano, TX, US (DFW-F3)
Under Maintenance
Madrid, Spain (MAD-F1)
Under Maintenance
Singapore (SIN-F3)
Under Maintenance
Toronto, Canada (YTO-F2)
Under Maintenance
Sydney, Australia (SYD-F2)
Under Maintenance
Paris, France (PAR-F4)
Under Maintenance
Frankfurt, Germany (FRA-F4)
Under Maintenance
São Paulo, Brazil (GRU-F1)
Under Maintenance
Vancouver, Canada (YVR-F3)
Under Maintenance
San Jose, CA, US (SJC-F4)
Under Maintenance
Burnaby, Canada (YVR-F4)
Under Maintenance
Ashburn, VA, US (IAD-F4)
Under Maintenance
Plano, TX, US (DFW-F4)
Under Maintenance
Madrid, Spain (MAD-F2)
Under Maintenance
Komagome, Japan (TYO-F4)
Under Maintenance
Auckland, New Zealand (AKL-F1)
Under Maintenance
London, United Kingdom (LON-F4)
Under Maintenance
Frankfurt, Germany (FRA-F5)
Under Maintenance
Toronto, Canada (YTO-F3)
Under Maintenance
Singapore (SIN-F4)
Under Maintenance
Miami, FL, US (MIA-F3)
Under Maintenance
Burnaby, Canada (YVR-F5)
Under Maintenance
Bangalore, India (BLR-F2)
Under Maintenance
Ashburn, VA, US (IAD-F5)
Under Maintenance
Sydney, Australia (SYD-F3)
Under Maintenance
Dubai, UAE (DXB-F3)
Under Maintenance
Taipei, Taiwan (TPE-F1)
Under Maintenance
Ashburn, VA, US (IAD-F2)
Under Maintenance
Tokyo, Japan (TYO-F3)
Under Maintenance
San Jose, CA, US (SJC-F5)
Under Maintenance
Kamloops, Canada (YKA-F1)
Under Maintenance
Dubai, UAE (DXB-F4)
Under Maintenance
Paris, France (PAR-F5)
Under Maintenance
Leeds, United Kingdom (LBA-F1)
Under Maintenance
Burnaby, Canada (YVR-F6)
Under Maintenance
San Jose, CA, US (SJC-F6)
Under Maintenance
San Jose, CA, US (SJC-F7)
Under Maintenance
Public Cloud Locations
Under Maintenance
Johannesburg, South Africa (JNB-G2)
Under Maintenance
Tel Aviv, Israel (TLV-G1)
Under Maintenance
Hamina, Finland (HEL-G2)
Under Maintenance
Eemshaven, Netherlands (AMS-G2)
Under Maintenance
Tel Aviv, Israel (TLV-G2)
Under Maintenance
Madrid, Spain (MAD-G2)
Under Maintenance
Melbourne, Australia (MEL-G2)
Under Maintenance
Santiago, Chile (SCL-G2)
Under Maintenance
Seoul, South Korea (SEL-G2)
Under Maintenance
Doha, Qatar (DOH-G2)
Under Maintenance
Ashburn, VA, US (IAD-G2)
Under Maintenance
The Dalles, OR, US (PDX-G2)
Under Maintenance
Jakarta, Indonesia (JKT-G2)
Under Maintenance
Milan, Italy (MIL-G2)
Under Maintenance
São Paulo, Brazil (SAO-G2)
Under Maintenance
Mumbai, India (BOM-G2)
Under Maintenance
Las Vegas, NV, US (LAS-G2)
Under Maintenance
Dammam, Saudi Arabia (DMM-G2)
Under Maintenance
Taipei, Taiwan (TPE-G2)
Under Maintenance
Osaka, Japan (OSA-G2)
Under Maintenance
Hong Kong, China (HKG-G2)
Under Maintenance
Dallas, TX, US (DFW-G2)
Under Maintenance
Sydney, Australia (SYD-G2)
Under Maintenance
Querétaro, Mexico (QRO-G2)
Under Maintenance
Dublin, Ireland (DUB-A1)
Under Maintenance
Perth, Australia (PER-A1)
Under Maintenance
Auckland, New Zealand (AKL-A1)
Under Maintenance
Delhi, India (DEL-G2)
Under Maintenance
Chicago, IL, US (ORD-A1)
Under Maintenance
Zurich, Switzerland (ZRH-G2)
Under Maintenance
Warsaw, Poland (WAW-G2)
Under Maintenance
Buenos Aires, Argentina (BUE-A1)
Under Maintenance
St. Ghislain, Belgium (BRU-G2)
Under Maintenance
Lima, Peru (LIM-A1)
Under Maintenance
London, United Kingdom (LON-G2)
Under Maintenance
Manila, Philippines (MNL-A1)
Under Maintenance
Toronto, Canada (YTO-G2)
Under Maintenance
Paris, France (PAR-G2)
Under Maintenance
Frankfurt, Germany (FRA-G2)
Under Maintenance
Singapore (SIN-G2)
Under Maintenance
Miami, FL, US (MIA-A1)
Under Maintenance
Montreal, Canada (YMQ-G2)
Under Maintenance
Tokyo, Japan (TYO-G2)
Under Maintenance
Bangkok, Thailand (BKK-A1)
Under Maintenance
Columbus, OH, US (CMH-G2)
Under Maintenance
Moncks Corner, SC, US (CHS-G2)
Under Maintenance
Cyberjaya, Malaysia (KUL-A1)
Under Maintenance
Bogotá, Colombia (BOG-O1)
Under Maintenance
Vinhedo, Brazil (VCP-O1)
Under Maintenance
Paris, France (PAR-O1)
Under Maintenance
Mumbai, India (BOM-O1)
Under Maintenance
Sydney, Australia (SYD-O1)
Under Maintenance
London, United Kingdom (LON-O1)
Under Maintenance
Milan, Italy (MIL-O1)
Under Maintenance
Frankfurt, Germany (FRA-O1)
Under Maintenance
Jeddah, Saudi Arabia (JED-O1)
Under Maintenance
Abu Dhabi, UAE (AUH-O1)
Under Maintenance
Ashburn, VA, US (IAD-O1)
Under Maintenance
Stockholm, Sweden (STO-O1)
Under Maintenance
Chicago, IL, US (ORD-O1)
Under Maintenance
Osaka, Japan (OSA-O1)
Under Maintenance
Montreal, Canada (YMQ-O1)
Under Maintenance
Melbourne, Australia (MEL-O1)
Under Maintenance
Amsterdam, Netherlands (AMS-O1)
Under Maintenance
Santiago, Chile (SCL-O1)
Under Maintenance
Dubai, UAE (DXB-O1)
Under Maintenance
Monterrey, Mexico (MTY-O1)
Under Maintenance
Riyadh, Saudi Arabia (RUH-O1)
Under Maintenance
KSA Cloud Regions
Operational
Dammam Zone B
Operational
Dammam Zone C
Operational
Riyadh
Operational
Jeddah
Operational
FortiSASE Services
Under Maintenance
FortiSASE Portal
Under Maintenance
Endpoint Management
Under Maintenance
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
End-of-Life Datacenter Announcement - San Jose (SJC-F1, SJC-F2, SJC-F3) & Vancouver (YVR-F2, YVR-F3) Sep 15, 2026 00:00 - Oct 1, 2026 00:00 UTC
Effective September 15, 2026, the Legacy San Jose (SJC-F1, SJC-F2, and SJC-F3) and Vancouver (YVR-F2, YVR-F3) PoPs will reach End-of-Life (EOL) and will stop accepting new connections.
Fortinet is continuously enhancing the scalability and performance of the FortiSASE platform. To support our long-term strategy and improve overall stability, Fortinet is upgrading all Security PoPs to next-generation architecture. Customers who transition will benefit from improved stability, scalability, and performance for the duration of their service term.
Existing customer instances in these locations will continue to operate normally until September 15, 2026. After that date, the affected PoPs will be incrementally removed from customer environments, and customers may observe brief interruptions in access to the customer portal as remaining connections are transitioned.
Fortinet strongly recommends migrating to alternate PoPs ahead of this schedule. The Infrastructure page of the customer portal shows whether your environment includes any of the affected PoPs, and in-scope customers will see a migration interface there with next steps. San Jose, CA, US (SJC-F4, SJC-F5) and Burnaby, BC, CA (YVR-F5) are available as alternate locations for these regions, but any available PoP (based on license tier) can be selected. Customers who take no action before the deadline will be able to add a replacement PoP at any time.
If you have any questions regarding this activity, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #596658
Posted on Aug 27, 2026 - 22:09 UTC
Fortinet is continuously enhancing the scalability and performance of the FortiSASE platform. To support our long-term strategy and improve overall stability, Fortinet is upgrading all Security PoPs to next-generation architecture. Customers who transition will benefit from improved stability, scalability, and performance for the duration of their service term.
Existing customer instances in these locations will continue to operate normally until September 15, 2026. After that date, the affected PoPs will be incrementally removed from customer environments, and customers may observe brief interruptions in access to the customer portal as remaining connections are transitioned.
Fortinet strongly recommends migrating to alternate PoPs ahead of this schedule. The Infrastructure page of the customer portal shows whether your environment includes any of the affected PoPs, and in-scope customers will see a migration interface there with next steps. San Jose, CA, US (SJC-F4, SJC-F5) and Burnaby, BC, CA (YVR-F5) are available as alternate locations for these regions, but any available PoP (based on license tier) can be selected. Customers who take no action before the deadline will be able to add a replacement PoP at any time.
If you have any questions regarding this activity, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #596658
Posted on Aug 27, 2026 - 22:09 UTC