Completed
The scheduled maintenance has been completed.
Posted Jan 22, 2026 - 19:00 UTC
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Jan 22, 2026 - 11: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.4.c release include
For Feature release:
For new instances, support has been added for FortiClient 7.4.5 for FortiSASE desktop users.
For new instances, support has been added for next generation endpoint management where security posture tags and tagging rules can be created and managed together.
For new instances, as a remote user connectivity alternative when standard IPsec ports over UDP are blocked by networks, added support for IPsec over TCP with TCP port 443. This feature requires Windows or Mac endpoints running FortiClient 7.4.5 or later.
For new instances, added support for configuring DNS suffixes for IPsec tunnels in an endpoint profile. This feature requires Windows endpoints running FortiClient 7.4.5 or later.
For new instances, added a new rule type for security posture tagging based on CrowdStrike ZTA scores, which are generated by the CrowdStrike Falcon sensor, reflecting the endpoint's security posture. This feature requires Windows and Mac endpoints running FortiClient 7.4.5 or later.
For new instances, added support for ZTNA automatic login using OAuth. This feature requires valid supporting Entra ID configuration, Windows endpoints running FortiClient 7.4.5 or later, and FortiGate devices acting as a ZTNA application gateways running FortiOS 7.6.1 or later.
For new instances, FortiSASE can now learn security posture tags directly from FortiClient. This feature requires FortiClient 7.4.5 and later.
Added support for configuring and matching geography addresses as the source in policies which allow specific security profiles to be applied to remote user agents connecting from specific geolocations.
Added support for Public Cloud security PoPs: Bangkok - Thailand, Montreal - Canada, Moncks Corner - South Carolina - USA, Tokyo - Japan.
For Mature release:
Added support for Public Cloud security PoPs: Montreal - Canada, Moncks Corner - South Carolina - USA, Tokyo - Japan.
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 #426123.
Posted Jan 16, 2026 - 21:55 UTC
This scheduled maintenance affected: Fortinet Cloud Locations (Dallas, TX, US (DFW-F1), Komagome, Japan (TYO-F1), San Jose, CA, US (SJC-F1), Singapore (SIN-F1), Sydney, Australia (SYD-F1), Tokyo, Japan (TYO-F2), Vancouver, Canada (YVR-F2), San Jose, CA, US (SJC-F2), Singapore(SIN-F2), Dallas, TX, US (DFW-F2), San Jose, CA, US (SJC-F3), Plano, TX, US (DFW-F3), Singapore(SIN-F3), Sydney, Australia (SYD-F2), Vancouver, Canada (YVR-F3), San Jose, CA, US (SJC-F4), Burnaby, Canada (YVR-F4), Plano, Texas USA (DFW-F4)) and Public Cloud Locations (Seoul, South Korea (SEL-G2), Portland, OR, US (PDX-G2), Las Vegas, NV, US (LAS-G2), Osaka, Japan (OSA-G2), Dallas,TX,US (DFW-G2), Querétaro, Mexico (QRO-G2), Chicago, IL, US (ORD-A1), Singapore (SIN-G2)).