Forticlient Cloud had 20 outages in the last 2 years totaling 76h 46m of downtime — averaging 0.8 incidents per month.
There were 20 Forticlient Cloud outages since June 14, 2024 totaling 76h 46m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
We are continuing to investigate this issue.
This incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
There is currently an issue at backend on US and the team is investigating.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
A small number of Dubai customers are experiencing issues accessing EMS and may not be able to access it. We are investigating now. We apologize for any inconvenience this may cause, and thank you very much for your continued support.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We would like to inform you that our OpenStack is currently experiencing network degradation. This issue is impacting certain components of our infrastructure. Our teams are actively monitoring the situation. We apologize for any inconvenience and will keep you updated on progress. Thank you for your understanding.
This incident has been resolved.
There is currently an issue at backend on US and the team is investigating. It may affect new EMS instance provisioning.
This incident has been resolved.
A small number of Saudi Arabia customers are experiencing issues accessing EMS and may not be able to access it. We are investigating now. We apologize for any inconvenience this may cause, and thank you very much for your continued support.
This incident has been resolved. RCA: We have identified that the degraded service is due to one of the pods hitting a memory limit. As a result, some APIs and GUI access would fail intermittently. We have increased the memory limit to address this issue.
Customers are experiencing issues accessing EMS portal and may not be able to access it. We are investigate and fix the issue now. We apologize for any inconvenience this may cause, and thank you very much for your continued support.
This incident has been resolved.
We would like to inform you that our EMS Cloud is currently experiencing GUI and Portal Issue. FCT Telemetry remains fine. The team still investigating.. We apologize for any inconvenience and will keep you updated on progress.
This incident has been resolved.
We would like to inform you that our EMS Cloud is currently experiencing API and Portal Issue. FCT Telemetry remains fine. The team still investigating.. We apologize for any inconvenience and will keep you updated on progress. Thank you for your understanding.
We are continuing to investigate this issue.
This incident has been resolved.
There is currently a network failure on US SV10 and the NOC team is investigating. More information will be updated later.
The issue has been resolved .
This incident has been resolved.
This incident is isolated only to the Japan DC. At around 1.39 pm PST, after a batch of scheduled EMS upgrade, 158 nodes were put in "error" state. The issue already fixed by rollback and code change. RCA: The current analysis points to insufficient resources during the upgrade push for customers on Oct 8 which causes the nodes to hit the timeout threshold. As a result of hitting the timeout threshold, it is put in "ERROR" state. There's a faulty logic where if a node is "ASSIGNED" but in "ERROR" state, a new node will be provisioned and assigned. This causes the customer EMS to appear like a new EMS, however without any profiles.
A small number of Canadian customers are experiencing issues accessing EMS and may not be able to access it. RCA: The issue cause by Redis cache failure in Canada Control planes. Now restored.
We would like to inform you that our EMS Cloud is currently experiencing network degradation. This issue is impacting certain components of our infrastructure, resulting in slower response times and intermittent errors. Our teams are actively monitoring the situation. We apologize for any inconvenience and will keep you updated on progress. Thank you for your understanding.
This incident has been resolved.
We're experiencing a service outage with accessing the EMS cloud console. Our team is currently working to restore the service. We apologize for any inconvenience. FortiClient Cloud US users may be affected.
This incident has been resolved.