История сбоев Fortiweb Cloud

We are currently investigating this issue.

Dear customers, we have implemented mitigation measures and the service is now stable. We will continue to closely monitor the situation to ensure ongoing service reliability.

This incident has been resolved.

Action Recommendation: For customers **who added the A-record with LB IPs (20.50.222.94 AND 20.54.176.184)**, we kindly recommend updating your DNS A-records pointing to **20.107.95.65** at your earliest convenience to ensure uninterrupted service. If possible, we also recommend using a CNAME record instead of an A-record, which provides greater flexibility.

We are continuing to investigate this issue.

This incident has been resolved.

We are currently investigating this issue.

A fix has been implemented and we are monitoring the results.

The affected scrubbing servers have recovered and health checks have remained stable during the monitoring period. This incident is now resolved.

We are currently investigating this issue.

Previously 20.54.176.184 and 20.50.222.94 was down. Now they have recovered. Most applications have changed to serve by 20.107.95.65 and 20.107.95.95 since the previous incident. They are not affected by this incident.

We have successfully mitigated the DDoS attack variant, and traffic has now stabilized. If you have changed your application's A records from 20.50.222.94 and/or 20.54.176.184 to 20.107.95.65 and/or 20.107.95.95, please change them back to 20.50.222.94 and 20.54.176.184. We'll arrange to bring down the dynamic nodes (20.107.95.65 and 20.107.95.95). If your application uses CNAME record, you don't need to change it.

The affected scrubbing servers have recovered and health checks have remained stable during the monitoring period. This incident is now resolved.

We are continuing to investigate this issue.

Normally lb-3.eu-central-1.aws.waas-online.net has IP addresses 35.157.26.13 and 18.153.162.82. Currently the two nodes are under attack and they are not serving well. We have brought up nodes 3.71.235.211 and 3.73.142.131 and redirect lb-3.eu-central-1.aws.waas-online.net to the new nodes. Applications using CNAME records should be OK now. Applications using A records should change to 3.71.235.211 and 3.73.142.131 for better service.

The attacks are blocked. The original node are OK for several hours. Please recover your app's A records back to 35.157.26.13 and 18.153.162.82 if you have changed them to the new nodes. Nothing needs to be done for the applications using CNAME records.

We are currently investigating this issue.

A fix has been implemented and we are monitoring the results.

We have successfully mitigated the DDoS attack, and traffic has now stabilized. Application using A records of 3.71.235.211 and/or 3.73.142.131 should change back to 35.157.26.13 and 18.153.162.82. We'll arrange to bring down the dynamic nodes (3.71.235.211 and 3.73.142.131).

The affected scrubbing servers have recovered and health checks have remained stable during the monitoring period. This incident is now resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

This incident has been resolved.

In 01:08:20am June 12, 2026 Azure EU West (Netherlands) scurbbing servers down. We are investigate the issue now.

Load Balancer is not stable that cause traffic outage intermittently. Scale out standby to recover traffic.

All load balancer is recovered. Monitoring traffic for the next 30 mins

We are continuing to monitor for any further issues.

This incident has been resolved.

We are currently investigating an issue causing abnormal connection terminations for services in the us-east-2 (Ohio) region. Current Action: Our engineering teams are actively investigating the cause and working to restore normal service as quickly as possible.

We are continuing to investigate this issue.

We are aware of the ongoing service disruption caused by a DDoS attack. Our engineering team is coordinating with AWS emergency response specialists to mitigate the attack and restore normal operations. We will continue to provide updates as more information becomes available.

We are continuing to work on a fix for this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating an issue causing abnormal connection terminations for services in the us-east-2 (Ohio) region. Current Action: Our engineering teams are actively investigating the cause and working to restore normal service as quickly as possible. We will provide another update as soon as more information becomes available.

A specific traffic pattern caused the load balancing node to fail and go down. The issue has been temporarily resolved with an emergency workaround.

We identified a service incident affecting our Europe regions, where an incorrect configuration in the Request Limit module caused a large number of legitimate requests to be incorrectly blocked. Our team has applied a configuration fix and service behavior has returned to normal. We are continuing to monitor traffic and will provide a follow-up update including additional details and preventive actions.

We are monitoring a power-related event reported by Azure affecting a portion of the West US 2 region. At this time, services are operating normally; however, there is a potential risk of intermittent instability. We are closely monitoring the situation and will provide updates if there are any changes.

Azure has confirmed that the power-related issue in the West US 2 region has been fully resolved. Our services are operating normally, and no further impact is expected at this time. We will continue to monitor service health to ensure ongoing stability.

We are currently experiencing a major service outage that is affecting normal customer traffic. Some customers may be unable to access the service, or may experience timeouts, slow responses, or failed requests. Our engineering team is actively investigating the issue and working to restore normal operations as quickly as possible. We will provide further updates as soon as more information becomes available. Thank you for your patience and understanding.

This was caused by an error in the configuration of a new feature. We have identified the issue and implemented a temporary workaround to resolve the communication problem. We hope to resolve this issue completely within an hour.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We would like to inform you that multiple services are currently impacted due to an ongoing issue within the AWS infrastructure. AWS Notification( https://health.aws.amazon.com/health/status ): "[12:11 AM PDT] We are investigating increased error rates and latencies for multiple AWS services in the US-EAST-1 Region. We will provide another update in the next 30–45 minutes." Our team is actively monitoring the situation and working closely with AWS to minimize the impact. We will continue to provide updates as more information becomes available.

From AWS notification: [02:27 AM PDT] We are seeing significant signs of recovery. Most requests should now be succeeding. We continue to work through a backlog of queued requests. We will continue to provide additional information. We will continue to monitor until all services return to normal. Thank you for your patience.

Most AWS services have been restored, and the FortiAppSec Cloud Portal is back to normal as well.

We are currently investigating an issue causing abnormal connection terminations for services in the Azure - EU West region. Impact: The issue appears to be limited to a small number of sites that use an A-record to point directly to the 20.50.222.94 and 20.54.176.184 IP address due to LB connectivity issue. Current Status: Our engineering teams are restored LB connectivity becomes available and actively keep monitoring. Immediate Recommendation: For affected customers, we recommend temporarily adding the A-record pointing to **20.107.95.65, 20.107.95.95 AND 65.52.150.132** from your DNS configuration to mitigate the impact. Please keep the existing A-record IPs (20.50.222.94, 20.54.176.184) in place while adding the new ones. This approach ensures service continuity during the transition. If possible, we also recommend using a CNAME record instead of an A-record, which provides greater flexibility in handling future changes.

We are continuing to investigate this issue.

The LB connection has been restored. Our investigation confirms this is related to Azure network instability, with severe packet loss observed. We are urgently engaging with Azure technical support while continuing to monitor the situation closely.

The LB connectivity traffic has been restored. Action Recommendation: For customers **who added the A-record with temporary LB IPs (20.107.95.65, 20.107.95.95 AND 65.52.150.132)**, these addresses will continue to be available for the next 48 hours, we kindly recommend updating your DNS A-records pointing back to **20.50.222.94 and 20.54.176.184** at your earliest convenience to ensure uninterrupted service. If possible, we also recommend using a CNAME record instead of an A-record, which provides greater flexibility.

We are currently investigating an issue causing abnormal connection terminations for services in the Azure - EU West region. Impact: The issue appears to be limited to a small number of sites that use an A-record to point directly to the 20.50.222.94 and 20.54.176.184 IP address due to LB connectivity issue. Current Status: Our engineering teams are restored LB connectivity becomes available and actively keep monitoring. Immediate Recommendation: For affected customers, we recommend temporarily changing the A-record pointing from 20.50.222.94, 20.54.176.184 to **20.107.95.65, 20.107.95.95** from your DNS configuration to mitigate the impact. If possible, we also recommend using a CNAME record instead of an A-record, which provides greater flexibility in handling future changes.

The LB connectivity traffic has been restored. Action Recommendation: For customers **who switched the A-record to temporary LB IPs (20.107.95.65 and 20.107.95.95)**, these addresses will continue to be available for the next 48 hours, we kindly recommend updating your DNS A-records pointing back to **20.50.222.94 and 20.54.176.184** at your earliest convenience to ensure uninterrupted service. If possible, we also recommend using a CNAME record instead of an A-record, which provides greater flexibility.

We are currently investigating an issue causing abnormal connection terminations for services in the Azure - EU West region. Impact: The issue appears to be limited to a small number of sites that use an A-record to point directly to the 20.50.222.94, 20.54.176.184 IP address due to LB connectivity issue. Current Status: Our engineering teams are restored LB connectivity becomes available and actively keep monitoring. Immediate Recommendation: For affected customers, we recommend temporarily changing the A-record pointing from 20.50.222.94, 20.54.176.184 to **20.107.95.65, 20.107.95.95** from your DNS configuration to mitigate the impact.

Our investigation confirms this is related to Azure network instability, with severe packet loss observed. We are urgently engaging with Azure technical support while continuing to monitor the situation closely.

Update: The LB connectivity traffic has been restored. Action Recommendation: For customers **who switched the A-record to temporary LB IPs (20.107.95.65 and 20.107.95.95)**, these addresses will continue to be available for the next 48 hours, we kindly recommend updating your DNS A-records pointing back to **20.50.222.94 and 20.54.176.184** at your earliest convenience to ensure uninterrupted service.

This incident has been resolved.

There is an issue with the authentication service provided by FortiCloud. We have already contacted the FortiCloud team, and they are currently working on urgently investigating this problem.

We are continuing to investigate this issue.

We are continuing to investigate this issue with FortiCloud team

There is an issue with the authentication service provided by FortiCloud, and now the issue is resolved.

We have identified intermittent connectivity issues with FortiAppSec Cloud WAF scrubbing centres. This might cause issues with access to your applications. We are working on it with the highest priority and hope to solve it as soon as possible.

We are continuing to investigate this issue.

This incident has been resolved.