End-of-Life Datacenter Announcement - Dallas (DFW-F1, DFW-F2), Miami (MIA-F1, MIA-F2), Valbonne (NCE-F1), and Tokyo (TYO-F2, TYO-F3)
Subscribe
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 15, 2026 - 00:00 UTC
Oct 15, 2026 - 00:00 UTC
Scheduled - Effective October 15, 2026, the Legacy Dallas (DFW-F1, DFW-F2), Miami (MIA-F1, MIA-F2), Valbonne (NCE-F1), and Tokyo (TYO-F2, TYO-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 October 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 an alternate PoP before October 15, 2026. To check whether your environment is affected, visit the Infrastructure page of the FortiSASE portal. In-scope customers will see a migration interface there with next steps. Alternate PoPs are available in each affected region, and you may select any available PoP supported by your license tier. Customers who do not migrate before the deadline can still add a replacement PoP at any time afterward.
Branch on-ramp customers: New on-ramps must be configured and manually cut over before the EOL date. On-ramps not migrated by then will be decommissioned.
Thin-edge device customers: Contact FortiCare Support before enabling your replacement PoP, and reference Bug 1332461 for guidance.
If you have any questions regarding this activity, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #596658
Oct 15, 2026 00:00 - Nov 1, 2026 00:00 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 October 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 an alternate PoP before October 15, 2026. To check whether your environment is affected, visit the Infrastructure page of the FortiSASE portal. In-scope customers will see a migration interface there with next steps. Alternate PoPs are available in each affected region, and you may select any available PoP supported by your license tier. Customers who do not migrate before the deadline can still add a replacement PoP at any time afterward.
Branch on-ramp customers: New on-ramps must be configured and manually cut over before the EOL date. On-ramps not migrated by then will be decommissioned.
Thin-edge device customers: Contact FortiCare Support before enabling your replacement PoP, and reference Bug 1332461 for guidance.
If you have any questions regarding this activity, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #596658
Oct 15, 2026 00:00 - Nov 1, 2026 00:00 UTC
FortiSASE Network (AS40934)
Operational
Fortinet Cloud Locations
Under Maintenance
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
Singapore (SIN-F1)
Operational
Sydney, Australia (SYD-F1)
Operational
Tokyo, Japan (TYO-F2)
Operational
Toronto, Canada (YTO-F1)
Operational
Valbonne, France (NCE-F1)
Operational
Bangalore, India (BLR-F1)
Operational
Frankfurt, Germany (FRA-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
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
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
Burnaby, Canada (YVR-F6)
Operational
San Jose, CA, US (SJC-F6)
Operational
San Jose, CA, US (SJC-F7)
Operational
Frankfurt, Germany (FRA-F6)
Operational
Singapore (SIN-F5)
Operational
Madrid, Spain (MAD-F3)
Operational
Miami, FL, US (MIA-F4)
Operational
Hong Kong, China (HKG-F2)
Operational
London, United Kingdom (LON-F6)
Operational
Komagome, Japan (TYO-F5)
Operational
Ashburn, VA, US (IAD-F6)
Under Maintenance
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
Muscat (Oman) (MCT-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 Backend Maintenance Oct 26, 2026 17:00-23:00 UTC
Endpoint Management connections will reestablish, potentially delaying Telemetry updates up to 5 minutes during a single maintenance window.
As part of this migration, only customers with currently assigned EMS IP address 154.52.16.121 will change to 176.23.145.118.
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.
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #627571.
Posted on Oct 15, 2026 - 15:03 UTC
As part of this migration, only customers with currently assigned EMS IP address 154.52.16.121 will change to 176.23.145.118.
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.
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #627571.
Posted on Oct 15, 2026 - 15:03 UTC
FortiSASE Proactive Software Maintenance for KSA environment only - release 26.3.2 Oct 26, 2026 17:00-21:00 UTC
This maintenance is for the KSA environment only.
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.
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #633066
Posted on Oct 22, 2026 - 22:46 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.
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #633066
Posted on Oct 22, 2026 - 22:46 UTC
FortiSASE Proactive Software Maintenance - FortiSASE release 26.3.2 [Hotfix] Oct 27, 2026 17:00-21:00 UTC
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 #633067.
Posted on Oct 23, 2026 - 19:48 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 #633067.
Posted on Oct 23, 2026 - 19:48 UTC
FortiSASE Endpoint Management - Proactive Backend Maintenance Oct 28, 2026 17:00-23:00 UTC
Anticipated Impact:
Endpoint Management connections will reestablish, potentially delaying Telemetry updates up to 5 minutes during a single maintenance window.
As part of this migration, only customers with currently assigned EMS IP address 38.21.198.38 will change to 159.48.179.75.
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.
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #628204.
Posted on Oct 15, 2026 - 15:16 UTC
Endpoint Management connections will reestablish, potentially delaying Telemetry updates up to 5 minutes during a single maintenance window.
As part of this migration, only customers with currently assigned EMS IP address 38.21.198.38 will change to 159.48.179.75.
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.
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #628204.
Posted on Oct 15, 2026 - 15:16 UTC