Live status / Developer tools
FortiSASE has planned maintenance in progress.
FortiSASE has planned maintenance in progress according to its official source.
Signal updated 2d ago · Sep 15, 2026, 3:10 PM UTC
Current incident · started Aug 27, 2026, 10:09 PM UTC
End-of-Life Datacenter Announcement - San Jose (SJC-F1, SJC-F2, SJC-F3) & Vancouver (YVR-F2, YVR-F3)
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
Affected surface
Components
118 of 146 affected
Official incident text
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
Source text is preserved verbatim and paired with its retrieval time.Last 30 days · Status timeline
What changed
- Scheduled
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
- 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…
- Scheduled
Maintenance will begin as scheduled in 60 minutes.
- In Progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
- Scheduled
Maintenance will begin as scheduled in 60 minutes.
- In Progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.