- Detected by Pingoru
- Jul 08, 2026, 08:06 PM UTC
- Resolved
- Jul 08, 2026, 09:34 PM UTC
- Duration
- 1h 28m
Affected: 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.
Read the full incident report →
- Detected by Pingoru
- Jul 08, 2026, 03:06 PM UTC
- Resolved
- Jul 08, 2026, 08:30 PM UTC
- Duration
- 5h 23m
Affected: Dallas, TX, US (DFW-F1)Dallas, TX, US (DFW-F2)Plano, TX, US (DFW-F3)Plano, TX, US (DFW-F4)
Timeline · 3 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Jul 03, 2026, 02:03 PM UTC
- Resolved
- Jul 03, 2026, 03:05 PM UTC
- Duration
- 1h 2m
Affected: San Jose, CA, US (SJC-F1)San Jose, CA, US (SJC-F2)San Jose, CA, US (SJC-F3)
Timeline · 3 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Jun 26, 2026, 06:32 PM UTC
- Resolved
- Jun 26, 2026, 08:44 PM UTC
- Duration
- 2h 12m
Affected: Endpoint Management
Timeline · 5 updates
-
investigating Jun 26, 2026, 06:32 PM UTC
We are currently observing partial degradation of connectivity to Endpoint Management systems across multiple regions, with the most significant impact on West Coast US. Customers whose EMS is hosted in these regions may experience intermittent connectivity. We apologize for any inconvenience this may cause and will provide updates as we make progress 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 #529190.
-
investigating Jun 26, 2026, 06:50 PM UTC
We are continuing to investigate this issue.
-
identified Jun 26, 2026, 07:32 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jun 26, 2026, 07:56 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 26, 2026, 08:44 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 26, 2026, 11:23 AM UTC
- Resolved
- Jun 29, 2026, 07:45 PM UTC
- Duration
- 3d 8h
Affected: Bangalore, India (BLR-F1)Pune, India (PNQ-F1)Mumbai, India (BOM-G2)Delhi, India (DEL-G2)Bangalore, India (BLR-F2)
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- Jun 11, 2026, 07:07 PM UTC
- Resolved
- Jun 12, 2026, 02:47 AM UTC
- Duration
- 7h 39m
Affected: Endpoint Management
Timeline · 2 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 03:11 AM UTC
- Resolved
- Jun 10, 2026, 09:21 AM UTC
- Duration
- 6h 9m
Affected: Miami, FL, US (MIA-F1)Miami, FL, US (MIA-F2)
Timeline · 3 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- May 28, 2026, 05:45 PM UTC
- Resolved
- May 28, 2026, 07:55 PM UTC
- Duration
- 2h 9m
Timeline · 3 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- May 22, 2026, 02:55 PM UTC
- Resolved
- May 22, 2026, 08:08 PM UTC
- Duration
- 5h 12m
Affected: Endpoint ManagementLondon, United Kingdom (LON-G2)
Timeline · 4 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- May 14, 2026, 11:54 PM UTC
- Resolved
- May 15, 2026, 11:12 AM UTC
- Duration
- 11h 18m
Affected: Endpoint Management
Timeline · 3 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- May 12, 2026, 07:16 PM UTC
- Resolved
- May 13, 2026, 09:01 PM UTC
- Duration
- 1d 1h
Affected: Plano, TX, US (DFW-F3)Plano, TX, US (DFW-F4)
Timeline · 6 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 08:35 AM UTC
- Resolved
- May 06, 2026, 12:32 PM UTC
- Duration
- 3h 56m
Affected: Plano, TX, US (DFW-F3)Plano, TX, US (DFW-F4)
Timeline · 3 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- May 05, 2026, 09:51 PM UTC
- Resolved
- May 05, 2026, 10:36 PM UTC
- Duration
- 44m
Affected: Sydney, Australia (SYD-O1)
Timeline · 3 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2026, 06:53 AM UTC
- Resolved
- Apr 23, 2026, 03:14 PM UTC
- Duration
- 8h 20m
Affected: Istanbul, Turkey (IST-F1)
Timeline · 5 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Apr 04, 2026, 03:19 PM UTC
- Resolved
- Apr 05, 2026, 07:51 AM UTC
- Duration
- 16h 31m
Affected: Singapore (SIN-F1)Singapore (SIN-F2)Singapore (SIN-F3)
Timeline · 4 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Mar 18, 2026, 05:03 AM UTC
- Resolved
- Mar 20, 2026, 02:41 PM UTC
- Duration
- 2d 9h
Affected: Endpoint Management
Timeline · 7 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 11:53 AM UTC
- Resolved
- Apr 02, 2026, 01:50 PM UTC
- Duration
- 31d 1h
Affected: Dubai, UAE (DXB-A1)
Timeline · 8 updates
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 12:49 AM UTC
- Resolved
- Feb 20, 2026, 07:53 PM UTC
- Duration
- 19h 4m
Affected: Endpoint Management
Timeline · 3 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Jan 30, 2026, 08:00 AM UTC
- Resolved
- Jan 30, 2026, 09:37 PM UTC
- Duration
- 13h 36m
Affected: FortiSASE Portal
Timeline · 4 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Nov 24, 2025, 04:36 PM UTC
- Resolved
- Nov 24, 2025, 08:29 PM UTC
- Duration
- 3h 52m
Affected: Ashburn, VA, US (IAD-F1)Endpoint ManagementDubai, UAE (DXB-F1)San Jose, CA, US (SJC-F1)Bangalore, India (BLR-F1)San Jose, CA, US (SJC-F2)San Jose, CA, US (SJC-F3)Ashburn, VA, US (IAD-F3)
Timeline · 8 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 04:07 PM UTC
- Resolved
- Nov 19, 2025, 01:39 PM UTC
- Duration
- 21h 31m
Affected: Endpoint Management
Timeline · 2 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Oct 21, 2025, 01:03 PM UTC
- Resolved
- Oct 21, 2025, 11:18 PM UTC
- Duration
- 10h 14m
Affected: Endpoint Management
Timeline · 5 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 09:52 AM UTC
- Resolved
- Oct 22, 2025, 01:44 PM UTC
- Duration
- 2d 3h
Affected: FortiSASE Network (AS40934)
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Sep 25, 2025, 02:35 PM UTC
- Resolved
- Sep 26, 2025, 09:37 PM UTC
- Duration
- 1d 7h
Affected: FortiSASE Portal
Timeline · 5 updates
-
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.
Read the full incident report →
Notice September 24, 2025 - Detected by Pingoru
- Sep 24, 2025, 11:50 AM UTC
- Resolved
- Sep 24, 2025, 10:07 PM UTC
- Duration
- 10h 17m
Affected: FortiSASE Portal
Timeline · 2 updates
-
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.
Read the full incident report →
