FortiAppSec Cloud Outage History

FortiAppSec Cloud is up right now

FortiAppSec Cloud had 14 outages in the last 2 years totaling 488h 40m of downtime — averaging 0.6 incidents per month.

There were 14 FortiAppSec Cloud outages since April 17, 2025 totaling 488h 40m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.appsec.fortinet.com

Critical June 21, 2026

[Service Outage Notice] WAF Scrubbing Regions - AWS - US East (Ohio) and AWS - US East (N. Virginia) Scrubbing Servers Down.

Detected by Pingoru
Jun 21, 2026, 02:42 PM UTC
Resolved
Jun 23, 2026, 02:01 AM UTC
Duration
1d 11h
Affected: WAF Scrubbing Region - AWS - US East (Ohio)WAF Scrubbing Region - AWS - US East (N. Virginia)
Timeline · 3 updates
  1. investigating Jun 21, 2026, 02:42 PM UTC

    We are currently investigating this issue.

  2. investigating Jun 21, 2026, 10:52 PM UTC

    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.

  3. resolved Jun 23, 2026, 02:01 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 20, 2026

Connectivity Issues with Load Balancer Node in Azure - EU West Netherlands

Detected by Pingoru
Jun 20, 2026, 07:32 PM UTC
Resolved
Jun 23, 2026, 02:01 AM UTC
Duration
2d 6h
Affected: WAF Scrubbing Region - Azure - EU West (Netherlands)
Timeline · 4 updates
  1. investigating Jun 20, 2026, 07:32 PM UTC

    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.

  2. investigating Jun 20, 2026, 07:32 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jun 20, 2026, 07:48 PM UTC

    We are continuing to investigate this issue.

  4. resolved Jun 23, 2026, 02:01 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 16, 2026

[Service Outage Notice] WAF Scrubbing Region - AWS - US East (Ohio) Scrubbing Servers Down.

Detected by Pingoru
Jun 16, 2026, 01:00 PM UTC
Resolved
Jun 17, 2026, 10:43 PM UTC
Duration
1d 9h
Affected: WAF Scrubbing Region - AWS - US East (Ohio)
Timeline · 3 updates
  1. investigating Jun 16, 2026, 01:00 PM UTC

    We are currently investigating this issue.

  2. monitoring Jun 17, 2026, 02:41 AM UTC

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

  3. resolved Jun 17, 2026, 10:43 PM UTC

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

Read the full incident report →

Critical June 15, 2026

[Service Outage Notice] Europe Regions – Azure EU West (Netherlands) Scrubbing Servers Down.

Detected by Pingoru
Jun 15, 2026, 07:41 AM UTC
Resolved
Jun 17, 2026, 10:43 PM UTC
Duration
2d 15h
Affected: WAF Scrubbing Region - Azure - EU West (Netherlands)
Timeline · 4 updates
  1. investigating Jun 15, 2026, 07:41 AM UTC

    We are currently investigating this issue.

  2. monitoring Jun 15, 2026, 09:19 AM UTC

    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.

  3. monitoring Jun 17, 2026, 11:33 AM UTC

    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.

  4. resolved Jun 17, 2026, 10:43 PM UTC

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

Read the full incident report →

Major May 19, 2026

Connectivity Issues with Load Balancer Node in us-east-1

Detected by Pingoru
May 19, 2026, 02:03 AM UTC
Resolved
May 25, 2026, 05:10 PM UTC
Duration
6d 15h
Affected: WAF Scrubbing Region - AWS - US East (Ohio)WAF Scrubbing Region - AWS - US East (N. Virginia)
Timeline · 8 updates
  1. investigating May 19, 2026, 02:03 AM UTC

    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.

  2. investigating May 19, 2026, 02:05 AM UTC

    We are continuing to investigate this issue.

  3. investigating May 19, 2026, 02:35 AM UTC

    We are continuing to investigate this issue.

  4. investigating May 19, 2026, 03:49 AM UTC

    We are continuing to investigate this issue.

  5. identified May 19, 2026, 03:58 AM UTC

    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.

  6. identified May 19, 2026, 04:12 AM UTC

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

  7. monitoring May 19, 2026, 05:17 AM UTC

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

  8. resolved May 25, 2026, 05:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 13, 2026

Connectivity Issues with Load Balancer Node in us-east-2

Detected by Pingoru
May 13, 2026, 09:52 PM UTC
Resolved
May 14, 2026, 01:26 AM UTC
Duration
3h 34m
Affected: WAF Scrubbing Region - AWS - US East (Ohio)
Timeline · 2 updates
  1. investigating May 13, 2026, 09:52 PM UTC

    We are currently investigating an issue causing abnormal connection terminations for services in the us-east-2 (Oregon) 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.

  2. resolved May 14, 2026, 01:26 AM UTC

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

Read the full incident report →

Major January 30, 2026

[Service Incident Notice] Europe Regions – Request Limit module false-positive blocking

Detected by Pingoru
Jan 30, 2026, 04:30 AM UTC
Resolved
Jan 30, 2026, 04:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Feb 02, 2026, 10:20 AM UTC

    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.

Read the full incident report →

Major January 10, 2026

Potential Service Impact – West US 2 Region

Detected by Pingoru
Jan 10, 2026, 07:20 PM UTC
Resolved
Jan 10, 2026, 09:48 PM UTC
Duration
2h 28m
Affected: WAF Scrubbing Region - Azure - US West 2 (Washington)
Timeline · 2 updates
  1. monitoring Jan 10, 2026, 07:20 PM UTC

    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.

  2. resolved Jan 10, 2026, 09:48 PM UTC

    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.

Read the full incident report →

Critical December 11, 2025

Critical Incident — Service Disruption

Detected by Pingoru
Dec 11, 2025, 07:56 PM UTC
Resolved
Dec 12, 2025, 03:48 AM UTC
Duration
7h 51m
Affected: WAF Scrubbing Region - AWS - US East (Ohio)WAF Scrubbing Region - Azure - EU West (Netherlands)WAF Scrubbing Region - GCP - Europe West 3 (Frankfurt)WAF Scrubbing Region - GCP - US East 1 (South Carolina)WAF Scrubbing Region - AWS - US West (Oregon)WAF Scrubbing Region - Azure - Canada Central (Toronto)WAF Scrubbing Region - GCP - Europe West 8 (Milan)WAF Scrubbing Region - AWS - Israel (Tel Aviv)WAF Scrubbing Region - Azure - Australia East (New South Wales)WAF Scrubbing Region - AWS - Asia Pacific (Mumbai)WAF Scrubbing Region - GCP - Middle East (Tel Aviv)WAF Scrubbing Region - Azure - US Central (Iowa)WAF Scrubbing Region - AWS - Asia Pacific (AP-Singapore)WAF Scrubbing Region - Azure - US East 2 (Virginia)WAF Scrubbing Region - GCP - US West 1 (Oregon)WAF Scrubbing Region - AWS - US East (N. Virginia)WAF Scrubbing Region - Azure - Qatar Central (Doha)WAF Scrubbing Region - AWS - Asia Pacific (Hong Kong)WAF Scrubbing Region - Azure - Brazil South (Sao Paulo)WAF Scrubbing Region - AWS - US West (N. California)WAF Scrubbing Region - Azure - US East (Virginia)WAF Scrubbing Region - AWS - EU (Ireland)WAF Scrubbing Region - Azure - US West 2 (Washington)WAF Scrubbing Region - AWS - SA (Sao Paulo)WAF Scrubbing Region - AWS - EU (Milan)WAF Scrubbing Region - AWS - Asia Pacific (Sydney)WAF Scrubbing Region - AWS - EU (London)WAF Scrubbing Region - AWS - EU (Paris)WAF Scrubbing Region - AWS - EU (Frankfurt)WAF Scrubbing Region - AWS - Canada (Central)WAF Scrubbing Region - Azure - South Africa North (Johannesburg)WAF Scrubbing Region - AWS - Asia Pacific (Jakarta)
Timeline · 4 updates
  1. investigating Dec 11, 2025, 07:56 PM UTC

    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.

  2. identified Dec 11, 2025, 10:46 PM UTC

    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.

  3. monitoring Dec 12, 2025, 01:30 AM UTC

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

  4. resolved Dec 12, 2025, 03:48 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 20, 2025

Incident Notification – Service Impact Due to AWS Network Issues

Detected by Pingoru
Oct 20, 2025, 07:33 AM UTC
Resolved
Oct 20, 2025, 02:29 PM UTC
Duration
6h 55m
Affected: FortiAppSec Cloud Management PortalFortiCloud Unified SSO Service
Timeline · 3 updates
  1. identified Oct 20, 2025, 07:33 AM UTC

    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.

  2. monitoring Oct 20, 2025, 09:32 AM UTC

    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.

  3. resolved Oct 20, 2025, 02:29 PM UTC

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

Read the full incident report →

Major September 30, 2025

Connectivity Issues with Load Balancer Node in Azure - EU West

Detected by Pingoru
Sep 30, 2025, 05:26 PM UTC
Resolved
Oct 01, 2025, 05:57 PM UTC
Duration
1d
Affected: WAF Scrubbing Region - Azure - EU West (Netherlands)
Timeline · 4 updates
  1. investigating Sep 30, 2025, 05:26 PM UTC

    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.

  2. investigating Sep 30, 2025, 06:10 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Sep 30, 2025, 07:09 PM UTC

    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.

  4. resolved Oct 01, 2025, 05:57 PM UTC

    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.

Read the full incident report →

Major August 7, 2025

FortiAppSec Cloud Management Console Partial Outage

Detected by Pingoru
Aug 07, 2025, 08:53 AM UTC
Resolved
Aug 07, 2025, 11:13 AM UTC
Duration
2h 19m
Affected: FortiAppSec Cloud Management PortalFortiAppSec Cloud Management APIFortiCloud Unified SSO Service
Timeline · 5 updates
  1. investigating Aug 07, 2025, 08:53 AM UTC

    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.

  2. investigating Aug 07, 2025, 09:15 AM UTC

    We are continuing to investigate this issue.

  3. investigating Aug 07, 2025, 09:16 AM UTC

    We are continuing to investigate this issue.

  4. investigating Aug 07, 2025, 11:04 AM UTC

    We are continuing to investigate this issue with FortiCloud team

  5. resolved Aug 07, 2025, 11:13 AM UTC

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

Read the full incident report →

Major April 17, 2025

Connectivity issues - Platform - WAF

Detected by Pingoru
Apr 17, 2025, 06:30 PM UTC
Resolved
Apr 19, 2025, 02:38 AM UTC
Duration
1d 8h
Affected: WAF Scrubbing Region - Azure - Brazil South (Sao Paulo)
Timeline · 3 updates
  1. investigating Apr 17, 2025, 06:30 PM UTC

    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.

  2. investigating Apr 17, 2025, 06:39 PM UTC

    We are continuing to investigate this issue.

  3. resolved Apr 19, 2025, 02:38 AM UTC

    This incident has been resolved.

Read the full incident report →