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 591 (0%) |
Incidents, newest first
Major November 24, 2025 Upstream ISP Connectivity Incident 3h 52m Ashburn, VA, US (IAD-F1), Endpoint Management, Dubai, UAE (DXB-F1), San Jose, CA, US (SJC-F1) and 4 more
Started Nov 24, 2025, 04:36 PM UTC· resolved Nov 24, 2025, 08:29 PM UTC
- identified Nov 24, 2025, 04:36 PM UTC
We have identified an upstream ISP connectivity issue for BLR-F1 (Bangalore) & DXB-F1 (Dubai). We are actively working with our external service providers to fully restore connectivity. If you have any questions regarding this incident, please contact FortiCare Support ( https://www.fortinet.com/support/contact ) and reference FortiSASE Operations ticket #413421.
- identified Nov 24, 2025, 05:51 PM UTC
We are continuing to work on a fix for this issue.
- identified Nov 24, 2025, 05:51 PM UTC
Additional impact has been observed for Endpoint Management traffic in Bangalore and Dubai, as well as management traffic for San Jose and Ashburn PoPs. This incident should not have an impact on customer data flow, but may result in degradation/inability to access the SASE portal for customers in these locations.
- identified Nov 24, 2025, 05:51 PM UTC
We are continuing to work on a fix for this issue.
- identified Nov 24, 2025, 05:53 PM UTC
We are continuing to work on a fix for this issue.
- identified Nov 24, 2025, 05:55 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Nov 24, 2025, 06:15 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Nov 24, 2025, 08:29 PM UTC
Connectivity through the upstream provider has remained stable. This incident is considered resolved.
Notice November 18, 2025 Third-Party Service Disruptions - Cloudflare 21h 31m Endpoint Management
Started Nov 18, 2025, 04:07 PM UTC· resolved Nov 19, 2025, 01:39 PM UTC
- monitoring Nov 18, 2025, 04:07 PM UTC
We are aware of a global Cloudflare network issue. This impacted DNS resolution and Certificate Validation on endpoints as the CRL is behind Cloudflare. A fix was implemented by Cloudflare and we are seeing significant improvements. We will continue monitoring the situation. If you have any questions regarding this incident, please contact FortiCare Support ( https://www.fortinet.com/support/contact ) and reference FortiSASE Operations ticket #412357.
- resolved Nov 19, 2025, 01:39 PM UTC
This incident has been resolved.
Major October 21, 2025 Endpoint Management - Intermittent API Timeouts Observed 10h 14m Endpoint Management
Started Oct 21, 2025, 01:03 PM UTC· resolved Oct 21, 2025, 11:18 PM UTC
- investigating Oct 21, 2025, 01:03 PM UTC
We are currently experiencing an intermittent API timeout issue with backend infrastructure components affecting communication with Endpoint Management systems in USA- Plano 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 ( and reference FortiSASE Operations ticket #396858
- investigating Oct 21, 2025, 03:08 PM UTC
We are continuing to investigate this issue.
- identified Oct 21, 2025, 05:54 PM UTC
The infrastructure team has implemented a fix for the issue affecting our Plano datacenter. We're seeing positive signs of recovery across the environment, though some customer Endpoint Management instances continue to require stabilization work. Our team is actively working to fully restore all affected services. We apologize for the inconvenience and appreciate your patience.
- identified Oct 21, 2025, 11:12 PM UTC
We are continuing to work on a fix for this issue.
- resolved Oct 21, 2025, 11:18 PM UTC
This incident has been resolved.
Notice October 20, 2025 Third-Party Service Disruptions - AWS Outage (N. Virginia) 2d 3h FortiSASE Network (AS40934)
Started Oct 20, 2025, 09:52 AM UTC· resolved Oct 22, 2025, 01:44 PM UTC
- monitoring Oct 20, 2025, 09:52 AM UTC
We are aware of widespread service disruptions across the internet caused by an AWS DynamoDB outage in the US-East-1 (N. Virginia) region. While our core services remain operational, customers may have experienced issues accessing various third-party integrations, external services, and even this status page (which relies on AWS infrastructure). The cascading failures from this AWS outage affected numerous cloud providers and SaaS platforms globally, which may indirectly impact your workflows that depend on these external services. Our systems are functioning normally; however, we recognize that the broader internet ecosystem disruption may still affect your ability to conduct normal business operations. A fix was implemented by AWS and we are seeing significant improvements. We will continue monitoring the situation as AWS and other affected providers work toward resolution. If you have any questions regarding this incident, please contact FortiCare Support ( https://www.fortinet.com/support/contact ) and reference FortiSASE Operations ticket #396095.
- resolved Oct 22, 2025, 01:44 PM UTC
This incident has been resolved.
Major September 25, 2025 Customer Portal - Intermittent Authentication Issues 1d 7h FortiSASE Portal
Started Sep 25, 2025, 02:35 PM UTC· resolved Sep 26, 2025, 09:37 PM UTC
- investigating Sep 25, 2025, 02:35 PM UTC
We are currently experiencing an issue with FortiCare authentication which is intermittently impacting IAM sub-user accounts attempting to login to the FortiSASE portal. This incident does not impact customer instances or data flow. For an temporary workaround, we'd advise logging into the FortiSASE portal using the root e-mail principal. If you have any questions regarding this incident, please contact FortiCare Support ( https://www.fortinet.com/support/contact ) and reference FortiSASE Operations ticket #387692.
- monitoring Sep 25, 2025, 03:28 PM UTC
We have applied a workaround restoring portal access in affected regions. We are currently monitoring results.
- identified Sep 25, 2025, 04:01 PM UTC
Previously applied workaround only partially resolved the issue. Root cause has been identified. Updates to be provided as they become available.
- monitoring Sep 25, 2025, 05:20 PM UTC
A workaround has been applied, and we are observing improved results. The permanent fix is in development and being tracked via Bug ID 1207828. We will continue to monitor.
- resolved Sep 26, 2025, 09:37 PM UTC
The workaround has remained stable and the permanent fix will be applied as part of our proactive software maintenance next week. This incident has been resolved.
Notice September 24, 2025 Customer Portal - EMEA - Increased Errors Observed 10h 17m FortiSASE Portal
Started Sep 24, 2025, 11:50 AM UTC· resolved Sep 24, 2025, 10:07 PM UTC
- monitoring Sep 24, 2025, 11:50 AM UTC
We experienced a brief period of intermittent API timeouts affecting customer portal users in EMEA. This may have resulted in intermittent failures accessing the portal in EMEA. We have redirected traffic for this region to other portal regions while this is investigated. No additional impact 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 #387499.
- resolved Sep 24, 2025, 10:07 PM UTC
After confirming the issue is no longer occurring in the EMEA portal region and has remained stable, it has been returned to service. This incident is resolved.
Notice September 1, 2025 EMS service degradation in Frankfurt region 23h 41m Endpoint Management
Started Sep 01, 2025, 12:36 PM UTC· resolved Sep 02, 2025, 12:18 PM UTC
- identified Sep 01, 2025, 12:36 PM UTC
We are currently experiencing an issue with backend infrastructure which impacts customers with EMS hosted in the Frankfurt region. We apologize for any inconvenience caused due to this incident and will provide further updates as they become available If you have any questions regarding this incident, please contact FortiCare Support ( and reference FortiSASE Operations ticket #383716
- monitoring Sep 01, 2025, 01:20 PM UTC
A fix was implemented and we are monitoring the results.
- monitoring Sep 01, 2025, 03:12 PM UTC
After this period of monitoring, we do not see any connection discrepancies, and we see the EMS service to be fully restored.
- resolved Sep 02, 2025, 12:18 PM UTC
This incident has been resolved.
Major August 29, 2025 EMS Service degradation -Plano region 13h 20m Endpoint Management
Started Aug 29, 2025, 04:37 AM UTC· resolved Aug 29, 2025, 05:58 PM UTC
- investigating Aug 29, 2025, 04:37 AM UTC
We are currently experiencing an issue with backend infrastructure components which impacts the customer whose EMS is hosted in USA- Plano region. 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 #381641
- investigating Aug 29, 2025, 09:20 AM UTC
We have observed many tenant instances have recovered, but the incident is not yet fully resolved. More updates to follow.
- resolved Aug 29, 2025, 05:58 PM UTC
This incident has been resolved.
Notice August 27, 2025 Network Outage in Ashburn Fortinet Cloud PoP 1d 6h Ashburn, VA, US (IAD-F1)
Started Aug 27, 2025, 02:18 PM UTC· resolved Aug 28, 2025, 08:25 PM UTC
- monitoring Aug 27, 2025, 02:18 PM UTC
A network issue has been identified towards a single external ISP affecting our Ashburn PoP for customers utilizing dedicated IPs within the 209.40.109.0/24 subnet. If you have any questions regarding this incident, please contact FortiCare Support ( and reference FortiSASE Operations ticket #378267.
- monitoring Aug 27, 2025, 03:22 PM UTC
Connectivity to the problematic ISP has been disabled to ensure stability while they investigate the issue. We are continuing to monitor connectivity.
- resolved Aug 28, 2025, 08:25 PM UTC
Network connectivity has remained stable, incident is considered resolved.
Critical July 16, 2025 Network Outage in Vancouver Fortinet Cloud PoP 8h 17m Vancouver, Canada (YVR-F2)
Started Jul 16, 2025, 07:43 AM UTC· resolved Jul 16, 2025, 04:01 PM UTC
- investigating Jul 16, 2025, 07:43 AM UTC
A network issue has been identified at the Vancouver 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 #370389.
- investigating Jul 16, 2025, 10:29 AM UTC
Some affected instances are recovering, but there's more affected still. We're actively working on it.
- investigating Jul 16, 2025, 12:23 PM UTC
A partial fix has been implemented and we're seeing many resolutions in our monitoring, but we're still actively working with the infrastructure team to address the caused incident.
- monitoring Jul 16, 2025, 01:22 PM UTC
Situation has now normalized, we'll keep monitoring the affected tenants for any weird behaviours or resurgence.
- resolved Jul 16, 2025, 04:01 PM UTC
During our monitoring, everything was nominal, so we're proceeding to resolve this incident. For any further queries or still particular pertaining issue, please contact FortiCare Support.
Minor June 11, 2025 Bangalore - FortiSASE EMS Service Degradation 1d 1h Bangalore, India (BLR-F1)
Started Jun 11, 2025, 06:28 AM UTC· resolved Jun 12, 2025, 07:53 AM UTC
- investigating Jun 11, 2025, 06:28 AM UTC
We are currently experiencing an issue with backend infrastructure components within Bangalore PoP which impacts the customer whose EMS is hosted in Bangalore DC. We are applying workaround to allow the users connect to VPN without any issues however customer using ZTNA will still have impact during this time. 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 (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #361870
- identified Jun 11, 2025, 06:45 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jun 11, 2025, 06:46 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 12, 2025, 07:53 AM UTC
This incident has been resolved.
Critical May 28, 2025 Vancouver - YVR-F2 Network Incident 2h 40m Vancouver, Canada (YVR-F2)
Started May 28, 2025, 07:30 PM UTC· resolved May 28, 2025, 10:11 PM UTC
- investigating May 28, 2025, 07:30 PM UTC
A network issue has been identified at the YVR-F2 PoP and is currently 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 #360311.
- monitoring May 28, 2025, 07:40 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 28, 2025, 10:11 PM UTC
This incident has been resolved.
Minor May 16, 2025 BLR-F1 - Upstream ISP Connectivity Incident 2d 14h Bangalore, India (BLR-F1)
Started May 16, 2025, 07:49 PM UTC· resolved May 19, 2025, 10:44 AM UTC
- identified May 16, 2025, 07:49 PM UTC
A network issue has been identified at the BLR-F1 PoP impacting some routes to external destinations, and is currently in the process of being remediated. If you have any questions regarding this incident, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #359678.
- monitoring May 16, 2025, 08:07 PM UTC
A network incident within external ISP, Airtel, with reachability of specific destination networks was observed. The incident was resolved and we are following up with the ISP for root cause analysis. We will continue to monitor this situation.
- resolved May 19, 2025, 10:44 AM UTC
This incident has been resolved.
Notice April 2, 2025 Toronto - Increased latency for FortiGuard Web Rating and DNS Lookups 3h 49m Dallas, TX, US (DFW-F1), Frankfurt, Germany (FRA-F1), London, United Kingdom (LON-F1), Miami, FL, US (MIA-F1) and 17 more
Started Apr 02, 2025, 07:12 PM UTC· resolved Apr 02, 2025, 11:02 PM UTC
- investigating Apr 02, 2025, 07:12 PM UTC
We are observing increased latency related to FortiGuard Web Rating and DNS Lookups for customers connected to the Toronto PoP. This has been escalated to the FortiGuard team which is actively investigating. We will provide updates as they become available.
- investigating Apr 02, 2025, 08:36 PM UTC
We are continuing to investigate this issue.
- monitoring Apr 02, 2025, 11:01 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 02, 2025, 11:02 PM UTC
This incident has been resolved.
Notice March 3, 2025 Localized connectivity issue to Microsoft 365 - Toronto 2d 3h Toronto, Canada (YTO-F1), Toronto, Canada (YTO-F2)
Started Mar 03, 2025, 06:06 PM UTC· resolved Mar 05, 2025, 09:28 PM UTC
- investigating Mar 03, 2025, 06:06 PM UTC
We are actively investigating a localized connectivity issue to Microsoft 365 impacting the Toronto PoP. If you have any questions regarding this incident, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket 342090.
- monitoring Mar 03, 2025, 06:06 PM UTC
We temporarily disconnected our peering sessions with Microsoft, in order to utilize alternate routes. Connectivity is restored.
- resolved Mar 05, 2025, 09:28 PM UTC
This incident has been resolved.