FortiSASE Outage History
FortiSASE is up right nowPingoru has recorded 48 incidents for FortiSASE: 31 in the last 12 months and 7 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 5 | 38 of 720 (5%) |
| May 2026 | 6 | 49 of 744 (7%) |
| June 2026 | 4 | 94 of 720 (13%) |
| July 2026 | 3 | 8 of 744 (1%) |
| August 2026 | 1 | 0 of 744 (0%) |
| September 2026 | 4 | 14 of 720 (2%) |
| October 2026 | 2 | 1 of 516 (0%) |
Incidents, newest first
Minor October 19, 2026 FortiSASE Endpoint Management Service Degradation - Frankfurt EMS Communication Issue 34m Endpoint Management
Started Oct 19, 2026, 10:15 AM UTC· resolved Oct 19, 2026, 10:49 AM UTC
- identified Oct 19, 2026, 10:15 AM UTC
We are experiencing an issue with some of the backend affecting communication for EMS hosted in Frankfurt, Germany. The issue is isolated only to a very small subset of FortiSASE customers. The relevant team is already working on the fix and further updates will be shared as soon as we have additional details. If you have any questions regarding this incident, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #630155
- resolved Oct 19, 2026, 10:49 AM UTC
This incident has been resolved.
Major October 6, 2026 Report of inability to load FortiSASE GUI 16m FortiSASE Portal
Started Oct 06, 2026, 01:27 PM UTC· resolved Oct 06, 2026, 01:44 PM UTC
- investigating Oct 06, 2026, 01:27 PM UTC
We are investigating reports of intermittent inability to load FortiSASE GUI (https://portal.prod.fortisase.com/). We will provide further updates as they become available. If you have any questions regarding this incident, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #626185.
- identified Oct 06, 2026, 01:35 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Oct 06, 2026, 01:44 PM UTC
This incident has been resolved.
Notice September 27, 2026 User Authentication Issue 6h 29m Endpoint Management
Started Sep 27, 2026, 07:59 AM UTC· resolved Sep 27, 2026, 02:28 PM UTC
- investigating Sep 27, 2026, 07:59 AM UTC
We are investigating reports of user authentication issues. We are actively troubleshooting the cause and will provide updates as they become available. If you have any questions regarding this incident, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #616815.
- identified Sep 27, 2026, 10:37 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Sep 27, 2026, 12:51 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 27, 2026, 02:28 PM UTC
This incident has been resolved.
Notice September 15, 2026 FortiGuard DNS Rating Service - Slow Browsing in Select PoPs (UK, EU, APAC) 3h 37m London, United Kingdom (LON-F1), Paris, France (PAR-F1), Tokyo, Japan (TYO-F2), Johannesburg, South Africa (JNB-G2) and 18 more
Started Sep 15, 2026, 11:17 AM UTC· resolved Sep 15, 2026, 02:54 PM UTC
- identified Sep 15, 2026, 11:17 AM UTC
We are investigating an issue affecting FortiGuard DNS rating lookups (SDNS) for customers using DNS Filter profiles connected to PoPs in the United Kingdom, France, Netherlands, Japan, South Korea and South Africa regions. General internet traffic and DNS resolution through the affected PoPs continue to work normally. Some web browsing may be slower than usual while DNS rating requests are delayed. We're currently pushing a hotfix to all affected regions. If you have any questions regarding this incident, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #606150.
- monitoring Sep 15, 2026, 01:00 PM UTC
The hotfix has been pushed to the majority of the affected instances and everything is running accordingly. We're currently monitoring and have raised internally a root cause investigation.
- resolved Sep 15, 2026, 02:54 PM UTC
This incident has been resolved.
Minor September 4, 2026 FortiSASE Endpoint Management Service Degradation 1h 21m Endpoint Management
Started Sep 04, 2026, 10:12 PM UTC· resolved Sep 04, 2026, 11:33 PM UTC
- investigating Sep 04, 2026, 10:12 PM UTC
We are currently experiencing an issue with backend infrastructure components within Frankfurt PoP which impacts the customer whose EMS is hosted in Frankfurt DC. We apologize for any inconvenience cause due to this issue and will keep updated on the progress. If you have any questions regarding this incident, please contact FortiCare Support ( and reference FortiSASE Operations ticket #599938
- monitoring Sep 04, 2026, 10:29 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 04, 2026, 11:33 PM UTC
This incident has been resolved.
Notice September 4, 2026 FortiCare Authentication Issue 2h FortiSASE Portal
Started Sep 04, 2026, 07:17 PM UTC· resolved Sep 04, 2026, 09:17 PM UTC
- investigating Sep 04, 2026, 07:17 PM UTC
We are currently experiencing an issue with FortiCare authentication which is affecting access to multiple FortiCloud services. This incident does not impact customer instances or data flow. However, users may be unable to log in to the FortiSASE portal as a result of this incident. If you have any questions regarding this incident, please contact FortiCare Support ( and reference FortiSASE Operations ticket #599713.
- monitoring Sep 04, 2026, 08:06 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 04, 2026, 09:17 PM UTC
This incident has been resolved.
Minor August 28, 2026 API Reachability Issue for Columbus (CMH-G2) Tenants 12m Columbus, OH, US (CMH-G2)
Started Aug 28, 2026, 03:53 PM UTC· resolved Aug 28, 2026, 04:05 PM UTC
- identified Aug 28, 2026, 03:53 PM UTC
We are actively investigating an issue affecting API reachability for tenants hosted in Columbus (CMH-G2). Customers in this region may experience timeouts or slow page loads within the FortiSASE Portal. Dataflow is not impacted. Traffic continues to be processed and secured normally, and no user-facing connectivity loss is expected. If you have any questions regarding this incident, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #596930
- monitoring Aug 28, 2026, 04:02 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 28, 2026, 04:05 PM UTC
This incident has been resolved.
Minor July 8, 2026 Network Incident - Public Cloud - Ohio 1h 28m Columbus, OH, US (CMH-G2)
Started Jul 08, 2026, 08:06 PM UTC· resolved Jul 08, 2026, 09:34 PM UTC
- investigating Jul 08, 2026, 08:06 PM UTC
We are investigating an intermittent network disruption impacting certain routes into the Columbus, Ohio Public Cloud region. Our engineering team has engaged and is actively working to identify the cause. If you have questions about this incident, please contact FortiCare Support and reference ticket #542406.
- monitoring Jul 08, 2026, 08:33 PM UTC
The cloud provider has confirmed a network incident affecting this region. Remediation is underway on their end, but the PoP has remained stable in the interim. We will continue to monitor. If you have questions about this incident, please contact FortiCare Support and reference ticket #542406.
- resolved Jul 08, 2026, 09:34 PM UTC
This incident has been resolved.
Notice July 8, 2026 FortiGuard Web Category Misclassification in Dallas and Plano 5h 23m Dallas, TX, US (DFW-F1), Dallas, TX, US (DFW-F2), Plano, TX, US (DFW-F3), Plano, TX, US (DFW-F4)
Started Jul 08, 2026, 03:06 PM UTC· resolved Jul 08, 2026, 08:30 PM UTC
- investigating Jul 08, 2026, 03:06 PM UTC
We are investigating an issue affecting customers connected to the Dallas and Plano PoPs where domains with an established rating in FortiGuard may be incorrectly classified as "Unrated" or "Newly Observed Domain" during category lookups. Domains that display a valid web category rating on fortiguard.com are being returned with an incorrect classification, which may result in unexpected policy enforcement behavior for affected traffic. This is being escalated to the FortiGuard team for review. We will provide updates as they become available. If you have questions regarding this incident, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #542286.
- monitoring Jul 08, 2026, 03:54 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 08, 2026, 08:30 PM UTC
This incident has been resolved.
Critical July 3, 2026 San José PoP - Service Disruption 1h 2m San Jose, CA, US (SJC-F1), San Jose, CA, US (SJC-F2), San Jose, CA, US (SJC-F3)
Started Jul 03, 2026, 02:03 PM UTC· resolved Jul 03, 2026, 03:05 PM UTC
- investigating Jul 03, 2026, 02:03 PM UTC
We are currently investigating a service disruption affecting the San José, California PoP. This location is no longer operational and customers routing traffic through this location may experience connectivity issues. Our engineering team is actively working on the issue and already reached out relevant team, thanks to let us provide further updates as soon as more information becomes available.
- monitoring Jul 03, 2026, 02:30 PM UTC
Connectivity to the San Jose infrastructure has been fully restored and all services are now operating normally. We will continue to monitor the situation to ensure stability.
- resolved Jul 03, 2026, 03:05 PM UTC
This incident has been resolved.
Notice June 26, 2026 Airtel Network Issue Impacting Inbound Connectivity to India PoPs 3d 8h Bangalore, India (BLR-F1), Pune, India (PNQ-F1), Mumbai, India (BOM-G2), Delhi, India (DEL-G2) and 1 more
Started Jun 26, 2026, 11:23 AM UTC· resolved Jun 29, 2026, 07:45 PM UTC
- identified Jun 26, 2026, 11:23 AM UTC
An issue on Airtel's network is impacting inbound connectivity from many North American networks to our India PoPs. Both Fortinet-operated and cloud-hosted PoPs across India are affected. SIA and SPA traffic to these PoPs may experience elevated latency and intermittent packet loss (upward of 30 to 40 percent). The issue is isolated to traffic traversing Airtel's network. Other paths into the region, as well as traffic within India, appear unaffected. Mitigation in progress: We proactively withdrew our eBGP advertisements to Airtel in Pune to steer traffic onto healthy paths, and we are applying the same change in Bangalore. External cloud providers have also been notified so they can adjust routing on their side as needed. Note that the observed behavior is occurring well outside our network, on provider-managed paths we do not control. If you have any questions regarding this incident, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #528142.
- monitoring Jun 26, 2026, 01:00 PM UTC
We completed the withdrawal of eBGP advertisements to Airtel in Bangalore, steering traffic onto healthy paths, and have continued monitoring since. Results have improved significantly, though some upstream paths through Airtel may still see impact in certain cases. Overall impact is reduced, and traffic will remain re-routed on Fortinet PoPs for the time being. The provider has reported a fiber cut impacting this international connectivity and is working with local authorities on a resolution. No provider fix is available yet for the affected paths. The observed behavior is occurring outside our network, on provider-managed paths we do not control, and the impacted external cloud provider has not yet provided any update on routing around the issue. We will continue monitoring and share further updates as the situation develops.
- resolved Jun 29, 2026, 07:45 PM UTC
The provider has confirmed that the affected path is now fully recovered. As a precaution, Airtel remains withdrawn from our eBGP peering for the India PoPs while we validate stability. We plan to reintroduce Airtel on July 1 with AS-path prepending applied, which will allow the path to carry traffic in a limited capacity while we continue to monitor performance. We are marking this incident as resolved. The remaining actions, including reintroducing Airtel and later fully restoring it as a standard provider in our routing blend, are routine and should not introduce any further customer impact.
Major June 11, 2026 Endpoint Management - Connection Errors Observed 7h 39m Endpoint Management
Started Jun 11, 2026, 07:07 PM UTC· resolved Jun 12, 2026, 02:47 AM UTC
- investigating Jun 11, 2026, 07:07 PM UTC
We are currently investigating a connectivity issue within backend infrastructure components, affecting communication with some of the Endpoint Management Systems in USA - Santa Clara region. We Apologize for any inconvenience caused due to this issue and will keep updated on the progress. If you have any questions regarding this incident, please contact FortiCare Support https://www.fortinet.com/support/contact and reference FortiSASE Operations ticket #508478
- resolved Jun 12, 2026, 02:47 AM UTC
This incident has been resolved.
Critical June 10, 2026 Power disruption at Miami DataCenter 6h 9m Miami, FL, US (MIA-F1), Miami, FL, US (MIA-F2)
Started Jun 10, 2026, 03:11 AM UTC· resolved Jun 10, 2026, 09:21 AM UTC
- investigating Jun 10, 2026, 03:11 AM UTC
We would like to inform you that the service disruption was caused by an unexpected power outage affecting our Miami Fortinet Cloud Location. The outage impacted critical infrastructure components within these facilities and resulted in temporary service degradation/interruption for affected customers. Upon detection, our operations and infrastructure teams immediately initiated incident response procedures, working with the data center provider to restore the services. The impact is currently limited only to mia-f1 and mia -f2. Instance with mia-f3 PoP is not impacted by this issue. We will share the next update by 3:08 am UTC.
- monitoring Jun 10, 2026, 04:37 AM UTC
We are pleased to inform you that power has been fully restored at the Miami Datacenter, and all affected services have resumed normal operations. Following the unexpected power disruption, our operations and facilities teams worked diligently to restore power and validate the stability of all affected systems. Services have now been restored and are operating normally. We continue to closely monitor the environment to ensure ongoing service stability. At this time, no further impact is expected. We sincerely apologize for any inconvenience caused by this incident and appreciate your patience and understanding throughout the restoration process. If you continue to experience any service issues, please contact FortiCare Support ( and reference FortiSASE Operations ticket #505678
- resolved Jun 10, 2026, 09:21 AM UTC
This incident has been resolved.
Notice May 28, 2026 FortiGuard DNS Lookup Issue 2h 9m
Started May 28, 2026, 05:45 PM UTC· resolved May 28, 2026, 07:55 PM UTC
- investigating May 28, 2026, 05:45 PM UTC
We are actively investigating an issue with DNS lookups when utilizing FortiGuard DNS (96.45.45.45, 96.45.46.46). This may result in connection failures to the Internet in cases where FortiGuard DNS is configured as the DNS server (under Configuration -> DNS within the SASE portal). If you have any questions regarding this incident, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #501065.
- monitoring May 28, 2026, 06:51 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 28, 2026, 07:55 PM UTC
This incident has been resolved.
Major May 22, 2026 LON-G2 (GCP London) - EMS Connectivity Issues 5h 12m Endpoint Management, London, United Kingdom (LON-G2)
Started May 22, 2026, 02:55 PM UTC· resolved May 22, 2026, 08:08 PM UTC
- identified May 22, 2026, 02:55 PM UTC
We have identified an incident impacting EMS connectivity only for the LON-G2 locations. Our engineering team are actively investigating the issue to determine the root cause and restore full service availability as quickly as possible. At this stage, the impact is limited to this specific region, and no other locations are currently affected. We will continue to provide regular updates on this status page as more information becomes available, including progress on the investigation and any remediation actions being taken. Thank you for your patience and understanding.
- identified May 22, 2026, 02:57 PM UTC
We are continuing to work on a fix for this issue.
- monitoring May 22, 2026, 06:56 PM UTC
A fix was implemented at 15:30 UTC and we have been monitoring the results.
- resolved May 22, 2026, 08:08 PM UTC
This incident has been resolved.
Minor May 14, 2026 FortiSASE EMS Service Degradation 11h 18m Endpoint Management
Started May 14, 2026, 11:54 PM UTC· resolved May 15, 2026, 11:12 AM UTC
- investigating May 14, 2026, 11:54 PM UTC
We are currently experiencing an issue with backend infrastructure components within San Jose & Plano PoPs which impacts the customer whose EMS is hosted in San Jose & Plano DCs. ZTNA traffic is impacted by this. We Apologize for any inconvenience cause due to this issue and will keep updated on the progress. If you have any questions regarding this incident, please contact FortiCare Support ( and reference FortiSASE Operations ticket #494467
- monitoring May 15, 2026, 05:04 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 15, 2026, 11:12 AM UTC
This incident has been resolved.
Critical May 12, 2026 Plano PoP - Network Disruption 1d 1h Plano, TX, US (DFW-F3), Plano, TX, US (DFW-F4)
Started May 12, 2026, 07:16 PM UTC· resolved May 13, 2026, 09:01 PM UTC
- investigating May 12, 2026, 07:16 PM UTC
A network issue has been identified at Plano PoP and is currently being investigated. 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 #490164.
- investigating May 13, 2026, 03:37 AM UTC
The team continues to investigate the issue. Work is ongoing to identify the root cause and restore the service. We will provide further updates as soon as more information becomes available.
- identified May 13, 2026, 03:50 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring May 13, 2026, 06:15 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring May 13, 2026, 10:12 AM UTC
We are continuing to monitor for any further issues.
- resolved May 13, 2026, 09:01 PM UTC
This incident has been resolved.
Major May 6, 2026 Plano PoP - Partial Network Disruption 3h 56m Plano, TX, US (DFW-F3), Plano, TX, US (DFW-F4)
Started May 06, 2026, 08:35 AM UTC· resolved May 06, 2026, 12:32 PM UTC
- investigating May 06, 2026, 08:35 AM UTC
A network issue has been identified at Plano PoP and is currently being investigated. 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 #485444.
- monitoring May 06, 2026, 10:34 AM UTC
After further investigation, the root cause of the outage reported has been identified, which was related to an issue that arose during a maintenance performed in this location. A fix has been implemented and we are currently monitoring the status.
- resolved May 06, 2026, 12:32 PM UTC
This incident has been resolved.
Major May 5, 2026 Sydney (SYD-O1) - Network Disruption 44m Sydney, Australia (SYD-O1)
Started May 05, 2026, 09:51 PM UTC· resolved May 05, 2026, 10:36 PM UTC
- identified May 05, 2026, 09:51 PM UTC
We are investigating a network issue at the Sydney, Australia (SYD-O1) PoP. 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 #485163
- monitoring May 05, 2026, 10:05 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 05, 2026, 10:36 PM UTC
This incident has been resolved.
Major April 23, 2026 Istanbul PoP - Partial Network Disruption 8h 20m Istanbul, Turkey (IST-F1)
Started Apr 23, 2026, 06:53 AM UTC· resolved Apr 23, 2026, 03:14 PM UTC
- investigating Apr 23, 2026, 06:53 AM UTC
A network issue has been identified at the Istanbul ist-f1 PoP and is currently being investigated. 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 #478728.
- identified Apr 23, 2026, 07:49 AM UTC
After further investigation, the root cause of the issue has been identified, our team is currently working to resolve this issue. Further updates will be shared as soon as we have additional details.
- monitoring Apr 23, 2026, 11:03 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Apr 23, 2026, 11:03 AM UTC
We are continuing to monitor for any further issues.
- resolved Apr 23, 2026, 03:14 PM UTC
This incident has been resolved.
Major April 4, 2026 Singapore - Partial Network Disruption 16h 31m Singapore (SIN-F1), Singapore (SIN-F2), Singapore (SIN-F3)
Started Apr 04, 2026, 03:19 PM UTC· resolved Apr 05, 2026, 07:51 AM UTC
- identified Apr 04, 2026, 03:19 PM UTC
A network issue has been identified at the Singapore PoP and is currently being investigated. Traffic has been automatically re-routed to other PoPs. If you have any questions regarding this incident, please contact FortiCare Support ( and reference FortiSASE Operations ticket #466814.
- identified Apr 04, 2026, 03:24 PM UTC
The issue has been identified and the relevant team is working on the fix.
- monitoring Apr 04, 2026, 06:13 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 05, 2026, 07:51 AM UTC
This incident has been resolved.
Critical March 18, 2026 Third-Party Service Disruptions - DNS 2d 9h Endpoint Management
Started Mar 18, 2026, 05:03 AM UTC· resolved Mar 20, 2026, 02:41 PM UTC
- investigating Mar 18, 2026, 05:03 AM UTC
We are investigating a widespread 3rd party DNS issue that impacts customers Turbo FQDN unreachable. We are escalating to the 3rd party and will update further information as as soon as possible. If you have any questions regarding this incident, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #457524.
- identified Mar 18, 2026, 05:38 AM UTC
We have identified an issue with a third-party DNS provider that may prevent managed endpoints from connecting to PoPs. Customers may experience degraded or interrupted access during this time. We are actively engaged with the provider and will share updates as soon as they are available.
- monitoring Mar 18, 2026, 06:18 AM UTC
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.
- monitoring Mar 18, 2026, 09:52 AM UTC
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.
- monitoring Mar 18, 2026, 09:04 PM UTC
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.
- monitoring Mar 19, 2026, 05:22 PM UTC
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.
- resolved Mar 20, 2026, 02:41 PM UTC
This incident has been resolved.
Minor March 2, 2026 Partial Outage – AWS UAE Infrastructure 31d 1h Dubai, UAE (DXB-A1)
Started Mar 02, 2026, 11:53 AM UTC· resolved Apr 02, 2026, 01:50 PM UTC
- monitoring Mar 02, 2026, 11:53 AM UTC
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.
- monitoring Mar 02, 2026, 11:53 AM UTC
We are continuing to monitor for any further issues.
- monitoring Mar 03, 2026, 11:53 AM UTC
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.
- monitoring Mar 03, 2026, 04:17 PM UTC
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.
- monitoring Mar 06, 2026, 02:24 PM UTC
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.
- monitoring Mar 16, 2026, 10:40 AM UTC
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.
- monitoring Mar 19, 2026, 06:05 PM UTC
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.
- resolved Apr 02, 2026, 01:50 PM UTC
This incident is considered resolved. Affected customers in this region were migrated during a scheduled maintenance window. Additionally, new provisioning into the impacted regions (Dubai DXB-A1, Oman MCT-A1) has been restricted until further notice.
Minor February 20, 2026 Certificate Rotation - FortiClient & SWG Connection Errors 19h 4m Endpoint Management
Started Feb 20, 2026, 12:49 AM UTC· resolved Feb 20, 2026, 07:53 PM UTC
- identified Feb 20, 2026, 12:49 AM UTC
We are aware of an issue related to Certificate Rotation which is causing connection errors for a small percentage of FortiClient and Secure Web Gateway (SWG) users. Our team is reviewing impacted tenants and applying remediations proactively. If you have any questions or require more rapid remediation, please contact FortiCare Support and reference FortiSASE Operations ticket #438337, bug ID #1259163.
- monitoring Feb 20, 2026, 05:47 AM UTC
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.
- resolved Feb 20, 2026, 07:53 PM UTC
This incident has been resolved.
Major January 30, 2026 Customer Portal - EMEA - Access Issue 13h 36m FortiSASE Portal
Started Jan 30, 2026, 08:00 AM UTC· resolved Jan 30, 2026, 09:37 PM UTC
- investigating Jan 30, 2026, 08:00 AM UTC
We are investigating reports of intermittent inability to load FortiSASE GUI ( and reference FortiSASE Operations ticket #432035.
- monitoring Jan 30, 2026, 09:07 AM UTC
The issue has been identified and a workaround has been implemented to restore portal access in affected regions. We are currently monitoring results.
- monitoring Jan 30, 2026, 11:09 AM UTC
The initial workaround resolved the issue for the majority of requests. However, a subset of users continued to experience SSO authentication failures when requests passed through the WAF. A secondary workaround has been applied to address this behavior. Root cause analysis is ongoing with our WAF Dev/QA teams. Preliminary findings indicate an issue with HTTP/2 traffic processing on a small percentage of EMEA nodes.
- resolved Jan 30, 2026, 09:37 PM UTC
We have deployed a hotfix to the WAF that addresses the root cause of this incident. All previously implemented workarounds have been reverted, and the environment has been confirmed stable. This incident is now fully resolved.