Monitoring - A network incident within external ISP, Airtel, with reachability of specific destination networks was observed. The incident was resolved and we are following up with the ISP for root cause analysis. We will continue to monitor this situation.
May 16, 2025 - 20:07 UTC
Identified - A network issue has been identified at the BLR-F1 PoP impacting some routes to external destinations, and is currently in the process of being remediated.
If you have any questions regarding this incident, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #359678.
May 16, 2025 - 19:49 UTC
FortiSASE Network (AS40934)
Operational
90 days ago
100.0
% uptime
Today
Fortinet Cloud Locations
Operational
90 days ago
100.0
% uptime
Today
Ashburn, VA, US (IAD-F1)
Operational
90 days ago
100.0
% uptime
Today
Dallas, TX, US (DFW-F1)
Operational
90 days ago
100.0
% uptime
Today
Dubai, UAE (DXB-F1)
Operational
90 days ago
100.0
% uptime
Today
Frankfurt, Germany (FRA-F1)
Operational
90 days ago
100.0
% uptime
Today
Hong Kong (HKG-F1)
Operational
90 days ago
100.0
% uptime
Today
Komagome, Japan (TYO-F1)
Operational
90 days ago
100.0
% uptime
Today
London, United Kingdom (LON-F1)
Operational
90 days ago
100.0
% uptime
Today
Miami, FL, US (MIA-F1)
Operational
90 days ago
100.0
% uptime
Today
Ottawa, Canada (YOW-F1)
Operational
90 days ago
100.0
% uptime
Today
Paris, France (PAR-F1)
Operational
90 days ago
100.0
% uptime
Today
San Jose, CA, US (SJC-F1)
Operational
90 days ago
100.0
% uptime
Today
Singapore (SIN-F1)
Operational
90 days ago
100.0
% uptime
Today
Sydney, Australia (SYD-F1)
Operational
90 days ago
100.0
% uptime
Today
Tokyo, Japan (TYO-F2)
Operational
90 days ago
100.0
% uptime
Today
Toronto, Canada (YTO-F1)
Operational
90 days ago
100.0
% uptime
Today
Valbonne, France (NCE-F1)
?
Operational
90 days ago
100.0
% uptime
Today
Vancouver, Canada (YVR-F2)
Operational
90 days ago
100.0
% uptime
Today
Bangalore, India (BLR-F1)
Operational
90 days ago
100.0
% uptime
Today
Frankfurt, Germany (FRA-F2)
Operational
90 days ago
100.0
% uptime
Today
San Jose, CA, US (SJC-F2)
Operational
90 days ago
100.0
% uptime
Today
Pune, India (PNQ-F1)
Operational
90 days ago
100.0
% uptime
Today
London, United Kingdom (LON-F2)
Operational
90 days ago
100.0
% uptime
Today
Paris, France (PAR-F2)
Operational
90 days ago
100.0
% uptime
Today
Singapore(SIN-F2)
Operational
90 days ago
100.0
% uptime
Today
Miami, FL, US (MIA-F2)
Operational
90 days ago
100.0
% uptime
Today
Dallas, TX, US (DFW-F2)
Operational
90 days ago
100.0
% uptime
Today
Istanbul, Turkey (IST-F1)
Operational
90 days ago
100.0
% uptime
Today
Johannesburg, South Africa (JNB-F1)
Operational
90 days ago
100.0
% uptime
Today
Dubai, UAE (DXB-F2)
Operational
90 days ago
100.0
% uptime
Today
San Jose, CA, US (SJC-F3)
Operational
90 days ago
100.0
% uptime
Today
Frankfurt, Germany (FRA-F3)
Operational
90 days ago
100.0
% uptime
Today
Paris,France(PAR-F3)
Operational
90 days ago
100.0
% uptime
Today
Ashburn, VA, US (IAD-F3)
Operational
90 days ago
100.0
% uptime
Today
London, United Kingdom (LON-F3)
Operational
90 days ago
100.0
% uptime
Today
Plano, TX, US (DFW-F3)
Operational
90 days ago
100.0
% uptime
Today
Madrid, Spain (MAD-F1)
Operational
90 days ago
100.0
% uptime
Today
Singapore(SIN-F3)
Operational
90 days ago
100.0
% uptime
Today
Toronto, Canada (YTO-F2)
Operational
90 days ago
100.0
% uptime
Today
Sydney, Australia (SYD-F2)
Operational
90 days ago
100.0
% uptime
Today
Paris,France (PAR-F4)
Operational
90 days ago
100.0
% uptime
Today
Frankfurt, Germany (FRA-F4)
Operational
90 days ago
100.0
% uptime
Today
São Paulo (GRU-F1)
Operational
90 days ago
100.0
% uptime
Today
Public Cloud Locations
Operational
90 days ago
100.0
% uptime
Today
Mombasa, Kenya (MBA-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Atlanta, GA, US (ATL-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Aurora, IL, US (ORD-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Austin, TX, US (AUS-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Columbus, OH, US (CMH-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Council Bluffs, IA, US (OMA-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Denver, CO, US (DEN-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Houston, TX, US (IAH-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Kansas City, MO, US (MCI-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Las Vegas, NV, US (LAS-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Minneapolis, MN, US (MSP-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Montreal, Canada (YUL-E1)
?
Operational
90 days ago
100.0
% uptime
Today
New York, NY, US (JFK-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Philadelphia, PA, US (PHL-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Phoenix, AZ, US (PHX-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Portland, OR, US (PDX-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Salt Lake City, UT, US (SLC-E1)
?
Operational
90 days ago
100.0
% uptime
Today
San Antonio, TX, US (SAT-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Boston, MA, US (BOS-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Querétaro, Mexico (QRO-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Bogotá, Colombia (BOG-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Buenos Aires, Argentina (EZE-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Rio de Janeiro, Brazil (GIG-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Santiago, Chile (SCL-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Amsterdam, Netherlands (AMS-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Athens, Greece (ATH-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Barcelona, Spain (BCN-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Brussels, Belgium (BRU-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Bucharest, Romania (OTP-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Budapest, Hungary (BUD-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Copenhagen, Denmark (CPH-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Dublin, Ireland (DUB-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Düsseldorf, Germany (DUS-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Geneva, Switzerland (GVA-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Hamburg, Germany (HAM-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Kyiv, Ukraine (KBP-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Lisbon, Portugal (LIS-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Madrid, Spain (MAD-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Manchester, UK (MAN-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Milan, Italy (MIL-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Oslo, Norway (OSL-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Prague, Czechia (PRG-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Rome, Italy (FCO-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Sofia, Bulgaria (SOF-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Stockholm, Sweden (ARN-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Turin, Italy (TRN-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Vienna, Austria (VIE-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Warsaw, Poland (WAW-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Zagreb, Croatia (ZAG-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Zürich, Switzerland (ZRH-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Dammam, Saudi Arabia (DMM-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Doha, Qatar (DOH-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Muscat, Oman (MCT-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Bangkok, Thailand (BKK-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Busan, South Korea (PUS-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Delhi, India (DEL-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Hsinchu, Taiwan (TPE-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Jakarta, Indonesia (CGK-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Kolkata, India (CCU-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Kuala Lumpur, Malaysia (KUL-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Manila, Philippines (MNL-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Mumbai, India (BOM-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Seoul, South Korea (SEL-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Taipei, Taiwan (TPE-E2)
?
Operational
90 days ago
100.0
% uptime
Today
Auckland, New Zealand (AKL-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Brisbane, Australia (BNE-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Canberra, Australia (CBR-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Melbourne, Australia (MEL-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Perth, Australia (PER-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Johannesburg, South Africa (JNB-G2)
?
Operational
90 days ago
100.0
% uptime
Today
Lagos, Nigeria (LOS-E1)
?
Operational
90 days ago
100.0
% uptime
Today
Milan, Italy (MIL-G1)
?
Operational
90 days ago
100.0
% uptime
Today
Tel Aviv, Israel (TLV-G1)
?
Operational
90 days ago
100.0
% uptime
Today
Hamina, Finland (HEL-G2)
?
Operational
90 days ago
100.0
% uptime
Today
Amsterdam, Netherlands (AMS-G2)
Operational
90 days ago
100.0
% uptime
Today
Tel Aviv, Israel (TLV-G2)
Operational
90 days ago
100.0
% uptime
Today
Madrid, Spain (MAD-G2)
Operational
90 days ago
100.0
% uptime
Today
Melbourne, Australia (MEL-G2)
Operational
90 days ago
100.0
% uptime
Today
Santiago, Chile (SCL-G2)
Operational
90 days ago
100.0
% uptime
Today
Seoul, South Korea (SEL-G2)
Operational
90 days ago
100.0
% uptime
Today
Doha, Qatar (DOH-G2)
Operational
90 days ago
100.0
% uptime
Today
Ashburn, VA,US (IAD-G2)
Operational
90 days ago
100.0
% uptime
Today
Portland, OR, US (PDX-G2)
Operational
90 days ago
100.0
% uptime
Today
Jakarta, Indonesia (JKT-G2)
Operational
90 days ago
100.0
% uptime
Today
Milan, Italy (MIL-G2)
?
Operational
90 days ago
100.0
% uptime
Today
Sao Paulo, Brazil (SAO-G2)
Operational
90 days ago
100.0
% uptime
Today
Calgary, Canada (YYC-E1)
Operational
90 days ago
100.0
% uptime
Today
Chicago, IL, US (CHI-E1)
Operational
90 days ago
100.0
% uptime
Today
Dallas, TX, US (DFW-E1)
Operational
90 days ago
100.0
% uptime
Today
Los Angeles, CA, US (LAX-E1)
Operational
90 days ago
100.0
% uptime
Today
Miami, FL, US (MIA-E1)
Operational
90 days ago
100.0
% uptime
Today
Palo Alto, CA, US (SFO-E1)
Operational
90 days ago
100.0
% uptime
Today
San Jose, CA, US (SJC-E1)
Operational
90 days ago
100.0
% uptime
Today
Santa Clara, CA, US (SJC-E2)
Operational
90 days ago
100.0
% uptime
Today
Seattle, WA, US (SEA-E1)
Operational
90 days ago
100.0
% uptime
Today
Toronto, Canada (YTO-E1)
Operational
90 days ago
100.0
% uptime
Today
Vancouver, Canada (YVR-E1)
Operational
90 days ago
100.0
% uptime
Today
Sao Paulo, Brazil (GRU-E1)
Operational
90 days ago
100.0
% uptime
Today
Berlin, Germany (BER-E1)
Operational
90 days ago
100.0
% uptime
Today
Frankfurt, Germany (FRA-E1)
Operational
90 days ago
100.0
% uptime
Today
London, UK (LON-E1)
Operational
90 days ago
100.0
% uptime
Today
Marseille, France (MRS-E1)
Operational
90 days ago
100.0
% uptime
Today
Munich, Germany (MUC-E1)
Operational
90 days ago
100.0
% uptime
Today
Paris, France (PAR-E1)
Operational
90 days ago
100.0
% uptime
Today
Dubai, UAE (DXB-E1)
Operational
90 days ago
100.0
% uptime
Today
Fujairah, UAE (FJR-E1)
Operational
90 days ago
100.0
% uptime
Today
Chennai, India (MAA-E1)
Operational
90 days ago
100.0
% uptime
Today
Hong Kong, China (HKG-E1)
Operational
90 days ago
100.0
% uptime
Today
Hyderabad, India (HYD-E1)
Operational
90 days ago
100.0
% uptime
Today
Osaka, Japan (KIX-E1)
Operational
90 days ago
100.0
% uptime
Today
Singapore (SIN-E1)
Operational
90 days ago
100.0
% uptime
Today
Tokyo, Japan (TYO-E1)
Operational
90 days ago
100.0
% uptime
Today
Sydney, Australia (SYD-E1)
Operational
90 days ago
100.0
% uptime
Today
Mumbai, India (BOM-G2)
Operational
90 days ago
100.0
% uptime
Today
Las Vegas, NV, US (LAS-G2)
Operational
90 days ago
100.0
% uptime
Today
Dammam, Saudi Arabia (DMM-G2)
Operational
90 days ago
100.0
% uptime
Today
Taipei, Taiwan (TPE-G2)
Operational
90 days ago
100.0
% uptime
Today
Osaka, Japan (OSA-G2)
Operational
90 days ago
100.0
% uptime
Today
Hong Kong, China (HKG-G2)
Operational
90 days ago
100.0
% uptime
Today
Dallas,TX,US (DFW-G2)
Operational
90 days ago
100.0
% uptime
Today
Sydney, Australia (SYD-G2)
Operational
90 days ago
100.0
% uptime
Today
Querétaro, Mexico (QRO-G2)
Operational
90 days ago
100.0
% uptime
Today
FortiSASE Services
Operational
90 days ago
99.97
% uptime
Today
FortiSASE Portal
Operational
90 days ago
99.95
% uptime
Today
Endpoint Management
Operational
90 days ago
100.0
% uptime
Today
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.
Related
No incidents or maintenance related to this downtime.
Anticipated Impact: San Jose, CA Endpoint Management tenants only – Endpoint Management connections will reestablish, potentially delaying ZTNA updates up to 5 minutes during a single maintenance window.
To enhance service resilience, the FortiSASE Operations team will migrate Endpoint Management tenants from San Jose, CA to Plano, TX. This will occur across a series of rolling maintenance windows. Each customer will be affected only once.
What to expect during your maintenance window: * EMS connectivity may reestablish, briefly affecting Endpoint Management functions including ZTNA rules. * Temporary impact may last up to 5 minutes. * Change in Endpoint Management egress IP address to 160.223.171.232.
Note: This maintenance does not impact overall data flow or network connectivity. If you use IP filtering for Endpoint Management (Domain Connector/LDAP), please ensure the new IP is added to avoid disruption.
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #357152. Posted on
May 08, 2025 - 17:11 UTC
Anticipated Impact: San Jose, CA Endpoint Management tenants only – Endpoint Management connections will reestablish, potentially delaying ZTNA updates up to 5 minutes during a single maintenance window.
To enhance service resilience, the FortiSASE Operations team will migrate Endpoint Management tenants from San Jose, CA to Plano, TX. This will occur across a series of rolling maintenance windows. Each customer will be affected only once.
What to expect during your maintenance window: * EMS connectivity may reestablish, briefly affecting Endpoint Management functions including ZTNA rules. * Temporary impact may last up to 5 minutes. * Change in Endpoint Management egress IP address to 160.223.171.232.
Note: This maintenance does not impact overall data flow or network connectivity. If you use IP filtering for Endpoint Management (Domain Connector/LDAP), please ensure the new IP is added to avoid disruption.
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #357152. Posted on
May 08, 2025 - 17:12 UTC
Anticipated Impact: San Jose, CA Endpoint Management tenants only – Endpoint Management connections will reestablish, potentially delaying ZTNA updates up to 5 minutes during a single maintenance window.
To enhance service resilience, the FortiSASE Operations team will migrate Endpoint Management tenants from San Jose, CA to Plano, TX. This will occur across a series of rolling maintenance windows. Each customer will be affected only once.
What to expect during your maintenance window: * EMS connectivity may reestablish, briefly affecting Endpoint Management functions including ZTNA rules. * Temporary impact may last up to 5 minutes. * Change in Endpoint Management egress IP address to 160.223.171.232.
Note: This maintenance does not impact overall data flow or network connectivity. If you use IP filtering for Endpoint Management (Domain Connector/LDAP), please ensure the new IP is added to avoid disruption.
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #357152. Posted on
May 08, 2025 - 17:14 UTC
Update -
This maintenance will be extended by 4 hours.
May 16, 2025 - 21:03 UTC
Scheduled -
San Jose, CA Endpoint Management tenants only – Endpoint Management connections will reestablish, potentially delaying ZTNA updates up to 5 minutes during a single maintenance window.
To enhance service resilience, the FortiSASE Operations team will migrate Endpoint Management tenants from San Jose, CA to Plano, TX. This will occur across a series of rolling maintenance windows. Each customer will be affected only once.
What to expect during your maintenance window: * EMS connectivity may reestablish, briefly affecting Endpoint Management functions including ZTNA rules. * Temporary impact may last up to 5 minutes. * Change in Endpoint Management egress IP address to 160.223.171.232.
Note: This maintenance does not impact overall data flow or network connectivity. If you use IP filtering for Endpoint Management (Domain Connector/LDAP), please ensure the new IP is added to avoid disruption.
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #357152.
May 08, 2025 - 17:16 UTC
Completed -
The scheduled maintenance has been completed.
May 13, 18:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 13, 10:00 UTC
Scheduled -
Anticipated Impact: San Jose, CA Analytics tenants only – Temporary disruption of real-time logging, log forwarding, and historical log access.
To enhance service resilience, the FortiSASE Operations team will migrate Analytics tenants from the San Jose, CA PoP to Plano, TX. This will occur across a series of rolling maintenance windows. Each customer will be affected only once.
What to expect during your maintenance window: * Temporary disruption of real-time logging and log forwarding. * Reset of historical log data available within the SASE portal. * Change in Log Forwarding egress IP to 209.40.123.198.
Note: This maintenance does not impact overall data flow or network connectivity. If you use IP filtering for Log Forwarding, please ensure the new IP is added to avoid disruption.
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #358763.
May 8, 16:45 UTC
Completed -
The scheduled maintenance has been completed.
May 12, 18:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 12, 10:00 UTC
Scheduled -
Anticipated Impact: San Jose, CA Analytics tenants only – Temporary disruption of real-time logging, log forwarding, and historical log access.
To enhance service resilience, the FortiSASE Operations team will migrate Analytics tenants from the San Jose, CA PoP to Plano, TX. This will occur across a series of rolling maintenance windows. Each customer will be affected only once.
What to expect during your maintenance window: * Temporary disruption of real-time logging and log forwarding. * Reset of historical log data available within the SASE portal. * Change in Log Forwarding egress IP to 209.40.123.198.
Note: This maintenance does not impact overall data flow or network connectivity. If you use IP filtering for Log Forwarding, please ensure the new IP is added to avoid disruption.
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #358763.
May 8, 16:43 UTC
Completed -
The scheduled maintenance has been completed.
May 9, 04:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 8, 22: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.
Features included in the 25.2.a release include:
* FortiClient 7.2.9 is the recommended supported version for existing and new FortiSASE instances using IPsec and SSL VPN remote user connectivity. * Added support to enhance default pre-logon tunnel security settings for IPsec by using stronger hashing algorithm (SHA 256) and key exchange algorithm (DH group 15) with IKE version 2. * Access to Fortinet or Regional Public Cloud Locations and features included with the Advanced remote users FortiSASE license are now supported with the Professional remote users FortiSASE license. - Network performance of Regional Public Cloud Locations differs from Public Cloud Locations supported with the Comprehensive license. - Since dedicated public IPs are provided by the Public Cloud provider, IP reputation control is not guaranteed, and source IP anchoring is not supported. * Added support for the Global Region Add-on license that can be added on top of an existing Comprehensive license. This add-on license entitles the instance to use an unlimited number of Security PoPs selected from existing and future Fortinet Cloud and Public Cloud locations. * Added support for registering FortiCASB data protection add-on licenses. * Number of private applications supported per agentless ZTNA bookmark policy increased from 20 to 200.
Resolved -
This incident has been resolved.
May 8, 05:20 UTC
Update -
We are continuing to monitor for any further issues.
May 8, 05:05 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
May 8, 05:04 UTC
Identified -
A network issue has been identified at the YVR-F2 PoP and is currently in the process of being remediated. Traffic has been automatically re-routed to other PoPs.
If you have any questions regarding this incident, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #358948.
May 8, 04:57 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.
Features included in the 25.2.a release include:
* FortiClient 7.2.9 is the recommended supported version for existing and new FortiSASE instances using IPsec and SSL VPN remote user connectivity. * Added support to enhance default pre-logon tunnel security settings for IPsec by using stronger hashing algorithm (SHA 256) and key exchange algorithm (DH group 15) with IKE version 2. * Access to Fortinet or Regional Public Cloud Locations and features included with the Advanced remote users FortiSASE license are now supported with the Professional remote users FortiSASE license. - Network performance of Regional Public Cloud Locations differs from Public Cloud Locations supported with the Comprehensive license. - Since dedicated public IPs are provided by the Public Cloud provider, IP reputation control is not guaranteed, and source IP anchoring is not supported. * Added support for the Global Region Add-on license that can be added on top of an existing Comprehensive license. This add-on license entitles the instance to use an unlimited number of Security PoPs selected from existing and future Fortinet Cloud and Public Cloud locations. * Added support for registering FortiCASB data protection add-on licenses. * Number of private applications supported per agentless ZTNA bookmark policy increased from 20 to 200.
Completed -
The scheduled maintenance has been completed.
May 7, 00:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 6, 18: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.
Features included in the 25.2.a release include:
* FortiClient 7.2.9 is the recommended supported version for existing and new FortiSASE instances using IPsec and SSL VPN remote user connectivity. * Added support to enhance default pre-logon tunnel security settings for IPsec by using stronger hashing algorithm (SHA 256) and key exchange algorithm (DH group 15) with IKE version 2. * Access to Fortinet or Regional Public Cloud Locations and features included with the Advanced remote users FortiSASE license are now supported with the Professional remote users FortiSASE license. - Network performance of Regional Public Cloud Locations differs from Public Cloud Locations supported with the Comprehensive license. - Since dedicated public IPs are provided by the Public Cloud provider, IP reputation control is not guaranteed, and source IP anchoring is not supported. * Added support for the Global Region Add-on license that can be added on top of an existing Comprehensive license. This add-on license entitles the instance to use an unlimited number of Security PoPs selected from existing and future Fortinet Cloud and Public Cloud locations. * Added support for registering FortiCASB data protection add-on licenses. * Number of private applications supported per agentless ZTNA bookmark policy increased from 20 to 200.
Completed -
The scheduled maintenance has been completed.
May 5, 21:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 5, 16: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 #358455.
May 1, 20:39 UTC