- Detected by Pingoru
- Apr 02, 2025, 07:12 PM UTC
- Resolved
- Apr 02, 2025, 11:02 PM UTC
- Duration
- 3h 49m
Affected: Dallas, TX, US (DFW-F1)Frankfurt, Germany (FRA-F1)London, United Kingdom (LON-F1)Miami, FL, US (MIA-F1)Ottawa, Canada (YOW-F1)Paris, France (PAR-F1)San Jose, CA, US (SJC-F1)Toronto, Canada (YTO-F1)Frankfurt, Germany (FRA-F2)San Jose, CA, US (SJC-F2)London, United Kingdom (LON-F2)Paris, France (PAR-F2)Miami, FL, US (MIA-F2)Dallas, TX, US (DFW-F2)San Jose, CA, US (SJC-F3)Frankfurt, Germany (FRA-F3)Paris,France(PAR-F3)London, United Kingdom (LON-F3)Toronto, Canada (YTO-F2)Paris,France (PAR-F4)Frankfurt, Germany (FRA-F4)
Timeline · 4 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2025, 06:06 PM UTC
- Resolved
- Mar 05, 2025, 09:28 PM UTC
- Duration
- 2d 3h
Affected: Toronto, Canada (YTO-F1)Toronto, Canada (YTO-F2)
Timeline · 3 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2025, 09:53 PM UTC
- Resolved
- Mar 03, 2025, 05:56 PM UTC
- Duration
- 3d 20h
Affected: FortiSASE Portal
Timeline · 3 updates
-
investigating Feb 27, 2025, 09:53 PM UTC
We are actively investigating intermittent FortiSASE Portal delays in loading Endpoint functionality, with occasional Internal Server Errors being presented. There is no impact to customer data flow. This issue has been escalated to the Development team which is actively investigating. We will provide updates as soon 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 340368.
-
monitoring Feb 28, 2025, 08:44 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 03, 2025, 05:56 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 22, 2025, 03:46 PM UTC
- Resolved
- Feb 25, 2025, 04:19 PM UTC
- Duration
- 3d
Affected: FortiSASE Portal
Timeline · 4 updates
-
investigating Feb 22, 2025, 03:46 PM UTC
We are actively investigating intermittent timeouts and failures for API calls related to Portal Login on some customer accounts. This may result in an intermittent inability to login to the FortiSASE Portal and impacts a small percentage of accounts. There is no impact to customer data flow. This issue has been escalated to the Development team which is actively investigating the issue, and we will provide updates as soon 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 334315.
-
monitoring Feb 22, 2025, 06:56 PM UTC
A temporary workaround has been implemented and we are monitoring the results. The development team has outlined the next steps for a permanent solution, with a hotfix release expected early next week.
-
monitoring Feb 25, 2025, 02:03 AM UTC
The associated hotfix release has been deployed and we are monitoring the results.
-
resolved Feb 25, 2025, 04:19 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 15, 2025, 07:06 PM UTC
- Resolved
- Feb 15, 2025, 08:35 PM UTC
- Duration
- 1h 29m
Affected: Endpoint Management
Timeline · 3 updates
-
identified Feb 15, 2025, 07:06 PM UTC
We are actively investigating intermittent timeouts and failures for API calls related to Endpoint Management. This may result in slow performance for Endpoint-related functions in the SASE Portal and occasional ZTNA tag match failures. This issue has been escalated to the EMS Cloud team which is actively investigating the issue, and we will provide updates as soon 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 330666.
-
monitoring Feb 15, 2025, 08:26 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 15, 2025, 08:35 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 14, 2025, 04:26 PM UTC
- Resolved
- Feb 14, 2025, 10:33 PM UTC
- Duration
- 6h 6m
Affected: Paris, France (PAR-F2)
Timeline · 3 updates
-
investigating Feb 14, 2025, 04:26 PM UTC
We are actively investigating a partial localized connectivity issue within the Paris PoP. This may result in connection failures in certain cases. Impacted instances have been proactively re-routed traffic from Paris PoP to other datacenters while this incident is remediated. If you have any questions regarding this incident, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket 329822.
-
monitoring Feb 14, 2025, 04:32 PM UTC
A fix was implemented. We’re observing that alarms associated with this incident have cleared, and are monitoring the results.
-
resolved Feb 14, 2025, 10:33 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 18, 2025, 11:45 PM UTC
- Resolved
- Jan 19, 2025, 01:28 AM UTC
- Duration
- 1h 43m
Affected: Vancouver, Canada (YVR-F2)
Timeline · 3 updates
-
identified Jan 18, 2025, 11:45 PM UTC
A network issue has been identified at the YVR-F2 PoP and is currently in the process of being remediated. 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 #263480.
-
monitoring Jan 19, 2025, 12:26 AM UTC
A fix was implemented. We're observing that alarms associated with this incident have cleared, and are monitoring the results.
-
resolved Jan 19, 2025, 01:28 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 10, 2024, 02:57 PM UTC
- Resolved
- Sep 24, 2024, 07:00 PM UTC
- Duration
- 14d 4h
Affected: FortiSASE Portal
Timeline · 3 updates
-
identified Sep 10, 2024, 02:57 PM UTC
We are investigating reports of intermittent inability to load FortiSASE GUI (https://portal.prod.fortisase.com/). Multiple reload attempts help to load the GUI. The issue has been escalated to the development team and is currently being investigated. 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 #180000.
-
monitoring Sep 10, 2024, 11:40 PM UTC
A fix was implemented at 21:30 (UTC) and we are monitoring the results. Please note: If still experiencing issues logging in with a secondary email account, this is due to the deprecation of FortiCare sub-accounts after the August release. Please convert your FortiCare users to IAM as documented here: https://docs.fortinet.com/document/forticloud/latest/identity-access-management-iam/508974/migration-of-existing-users
-
resolved Sep 24, 2024, 07:00 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 30, 2024, 07:24 PM UTC
- Resolved
- Aug 31, 2024, 08:01 AM UTC
- Duration
- 12h 36m
Affected: Ashburn, VA, US (IAD-F1)
Timeline · 3 updates
-
monitoring Aug 30, 2024, 07:24 PM UTC
We have received multiple reports of intermittent latency and timeouts for certain Internet paths in our Fortinet cloud location in Ashburn, VA. The impact of this appears to be isolated in nature to a small percentage of traffic. There will be an upstream maintenance performed outside of business hours for this location to attempt to remediate this behavior. If experiencing impact due to this behavior, please notify FortiCare Support to request temporary re-routing of traffic to other datacenters in your instance. We would like to apologize for any inconvenience. If you have any questions regarding this incident, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket 176398.
-
monitoring Aug 31, 2024, 12:17 AM UTC
A temporary workaround was implemented upstream, and the affected network paths have been stable with no degradation over the past few hours. A maintenance window is scheduled for the device which caused this incident on August 31 at 06:00 UTC. Our operations team is actively monitoring and will provide a final update once the incident is fully resolved.
-
resolved Aug 31, 2024, 08:01 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 05, 2024, 02:06 PM UTC
- Resolved
- Aug 05, 2024, 04:09 PM UTC
- Duration
- 2h 2m
Affected: Valbonne, France (NCE-F1)
Timeline · 3 updates
-
monitoring Aug 05, 2024, 02:06 PM UTC
We have identified a localized connectivity issue within the Valbonne, PoP. A fix is scheduled to be implemented today. We have proactively re-routed traffic from Valbonne, France to other datacenters while this incident is remediated. If you have any questions regarding this incident, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #164465.
-
monitoring Aug 05, 2024, 03:24 PM UTC
We are continuing to monitor for any further issues.
-
resolved Aug 05, 2024, 04:09 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2024, 07:16 PM UTC
- Resolved
- Jul 02, 2024, 07:29 PM UTC
- Duration
- 13m
Affected: FortiSASE Portal
Timeline · 2 updates
-
monitoring Jul 02, 2024, 07:16 PM UTC
We are investigating reports of SSO Authentication issues impacting the FortiSASE portal (https://portal.prod.fortisase.com/). The issue has been escalated to the responsible team and is currently being investigated. We 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 #155165.
-
resolved Jul 02, 2024, 07:29 PM UTC
A fix has been implemented.
Read the full incident report →
- Detected by Pingoru
- May 23, 2024, 07:40 PM UTC
- Resolved
- May 23, 2024, 10:04 PM UTC
- Duration
- 2h 23m
Affected: FortiSASE Portal
Timeline · 3 updates
-
investigating May 23, 2024, 07:40 PM UTC
We are investigating reports of SSO Authentication issues impacting the FortiSASE portal (https://portal.prod.fortisase.com/). The issue has been escalated to the responsible team and is currently being investigated. We 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 #145834.
-
monitoring May 23, 2024, 08:14 PM UTC
A workaround has been applied, and we are monitoring the results.
-
resolved May 23, 2024, 10:04 PM UTC
A fix has been implemented, issue resolved.
Read the full incident report →
