FortiSASE Outage History

A fix has been implemented and we are monitoring the results.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

The third-party provider has implemented a fix and we are starting to see successful DNS resolution to allow managed endpoints to connect to their PoPs, with some potential for added latency. We are monitoring the results.

Geoproximity-based DNS resolution continues to recover. Latency for new endpoint connections is improving as PoP assignment stabilizes. We are working with our vendor and monitoring closely.

Reports of geoproximity-based DNS resolution issues have largely resolved. Latency for new endpoint connections has improved significantly as PoP assignment stabilizes, and we expect any remaining impact to fully self-resolve as this process continues. For active cases still experiencing poor latency, we have a workaround available. Please contact support and reference this incident and our team can direct traffic to an alternate region while resolution completes. We are working with our vendor on full resolution and on identifying improvements to prevent recurrence. We apologize for any inconvenience and appreciate your patience.

We have received confirmation from our vendor that the underlying issue has been remediated and continue to monitor for any recurrence. All geoproximity-based DNS resolution appears to be operating normally and PoP assignments have stabilized. If you experience any further issues with geoproximity-based DNS resolution after reconnection, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference this incident. We appreciate your patience throughout this event.

We are currently monitoring an ongoing incident affecting AWS infrastructure in the United Arab Emirates. According to reports from AWS and public sources, an Availability Zone (mec1-az2) in the ME-CENTRAL-1 region was impacted after unidentified objects struck an AWS data center. As a safety precaution, local authorities cut power at the facility, resulting in a localized outage. Restoration of power and full connectivity is expected to take several hours. Other availability zones in the UAE are reported to be operational, but some FortiSASE services and resources in the affected zone may be unavailable or experience intermittent issues.

We are continuing to monitor for any further issues.

Services and resources hosted specifically in the impacted zone still experience temporary unavailability or intermittent connectivity. No impact has been observed outside the UAE region. We continue to monitor AWS service health and will provide updates as more information becomes available.

Due to the ongoing instability in the UAE region, Dubai (DXB-A1) has been temporarily excluded from the DNS resolution loop to prevent new connections from landing in the affected location. This also ensures users are automatically redirected to the next closest available PoP, preventing new connections from landing in the affected location.

The situation at the affected AWS UAE facilities remains unchanged. We continue to direct users to unaffected PoPs as the primary mitigation. Due to the unstable and inconsistent nature of infrastructure in DXB-A1, affected devices are experiencing varied behavior -- some show intermittent connectivity flapping resulting in API timeouts within the customer portal, while others remain completely offline. Out of an abundance of caution, we are not making topology changes to tenants in DXB-A1 at this time, and 26.1.1 upgrade windows for affected tenants have been deferred until the location is confirmed stable. We will continue to monitor and provide updates as the situation evolves.

We continue to monitor the situation affecting the AWS UAE infrastructure associated with DXB-A1. At this time, the conditions at the affected facilities remain unstable and no significant improvement has been observed. As a precaution, we are still avoiding any topology modifications for tenants currently hosted in DXB-A1 while the environment remains unstable. We are actively monitoring updates from AWS (https://health.aws.amazon.com/health/status?path=open-issues). Further updates will be provided as soon as new information becomes available or when the infrastructure stabilizes.

We have been monitoring ongoing instability affecting AWS UAE infrastructure at the DXB-A1 PoP. New provisioning at this location remains suspended, and it is not in use for data traffic. To improve portal stability for tenants in this region, we will be removing DXB-A1 from affected instances and applying the 26.1.1 release upgrade, which was previously deferred for impacted customers. This maintenance will be processed over three days, outside of local business hours (Mar 23, 2026 16:00 - Mar 26, 2026 16:00 UTC). No action is required on your part. Once maintenance is complete, you may provision at an alternative regional PoP. We recommend: Abu Dhabi, UAE (AUH-O1) If you have questions or would like to discuss migration options, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #457146.

Remediation has been applied to impacted tenants and we are continuing to monitor for full recovery. If you are still experiencing issues, please contact FortiCare Support and reference FortiSASE Operations ticket #438337, bug ID #1259163.