Is FortiSASE down?
Last checked 9m agoNo incidents right now.
FortiSASE is operational right now. Last checked 9m ago; the most recent incident resolved 18h ago.
Real-time FortiSASE status, recent outages, and incident history — pulled directly from FortiSASE's official status page at https://status.fortisase.com every 5 minutes. Pingoru tracks 146 FortiSASE services and has captured 31 incidents in the last 90 days (99.93% uptime). Get email, Slack, Discord, or webhook alerts the moment FortiSASE reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- London, United Kingdom (LON-F1)Paris, France (PAR-F1)Tokyo, Japan (TYO-F2)Johannesburg, South Africa (JNB-G2)Eemshaven, Netherlands (AMS-G2)Seoul, South Korea (SEL-G2)London, United Kingdom (LON-F2)Paris, France (PAR-F2)Johannesburg, South Africa (JNB-F1)Paris, France (PAR-F3)
Timeline · 3 updates
- 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.
Latest: This incident has been resolved.
-
- Endpoint Management
Timeline · 3 updates
- 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.
Latest: This incident has been resolved.
-
- FortiSASE Portal
Timeline · 3 updates
- 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.
Latest: This incident has been resolved.
-
- Columbus, OH, US (CMH-G2)
Timeline · 3 updates
- 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.
Latest: This incident has been resolved.
-
- Columbus, OH, US (CMH-G2)
Timeline · 3 updates
- 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.
Latest: This incident has been resolved.
-
See the full FortiSASE outage history
4 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse FortiSASE outage history →Or sign up free to get alerts when FortiSASE breaks · 10 free monitors · No credit card
- Started Sep 15, 2026, 11:17 AM UTC · Resolved Sep 15, 2026, 02:54 PM UTC · 3h 37m
- Started Sep 04, 2026, 10:12 PM UTC · Resolved Sep 04, 2026, 11:33 PM UTC · 1h 21m
- FortiCare Authentication Issue ResolvedStarted Sep 04, 2026, 07:17 PM UTC · Resolved Sep 04, 2026, 09:17 PM UTC · 2h
- Started Aug 28, 2026, 03:53 PM UTC · Resolved Aug 28, 2026, 04:05 PM UTC · 12m
- Started Jul 08, 2026, 08:06 PM UTC · Resolved Jul 08, 2026, 09:34 PM UTC · 1h 28m
- Started Jul 08, 2026, 03:06 PM UTC · Resolved Jul 08, 2026, 08:30 PM UTC · 5h 23m
- San José PoP - Service Disruption ResolvedStarted Jul 03, 2026, 02:03 PM UTC · Resolved Jul 03, 2026, 03:05 PM UTC · 1h 2m
- Started Jun 26, 2026, 06:32 PM UTC · Resolved Jun 26, 2026, 08:44 PM UTC · 2h 12m