Is FortiAppSec Cloud down?

Last checked 6m ago
Current status
FortiAppSec Cloud is up

No incidents right now.

Get alerts when FortiAppSec Cloud breaks → View FortiAppSec Cloud outage history →

Free · no credit card

Official status page: https://status.appsec.fortinet.com · Polled every 5 minutes · 44 components tracked

FortiAppSec Cloud is operational right now. Last checked 6m ago; the most recent incident resolved 3d ago.

Real-time FortiAppSec Cloud status, recent outages, and incident history — pulled directly from FortiAppSec Cloud's official status page at https://status.appsec.fortinet.com every 5 minutes. Pingoru tracks 44 FortiAppSec Cloud services and has captured 12 incidents in the last 90 days (99.37% uptime). Get email, Slack, Discord, or webhook alerts the moment FortiAppSec Cloud reports a new incident — free for 5 monitors, no credit card.

Users who monitor FortiAppSec Cloud also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 6,000+ providers
FortiAppSec Cloud uptime 99.37% uptime · past 90 days
Mon Wed Fri
MayJunJulAug
Less More

Recent outages & incidents

Past 90 days
  1. [Service Outage Notice] WAF Scrubbing Regions - AWS - US East (Ohio) and AWS - US East (N. Virginia) Scrubbing Servers Down.
    Resolved 1d 11h
    Started Jun 21, 2026, 02:42 PM UTC · Resolved Jun 23, 2026, 02:01 AM UTC
    WAF Scrubbing Region - AWS - US East (Ohio)WAF Scrubbing Region - AWS - US East (N. Virginia)
    Timeline · 3 updates
    • investigating · Jun 21, 2026, 02:42 PM UTC

      We are currently investigating this issue.

    • 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.

    • resolved · Jun 23, 2026, 02:01 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Connectivity Issues with Load Balancer Node in Azure - EU West Netherlands
    Resolved 2d 6h
    Started Jun 20, 2026, 07:32 PM UTC · Resolved Jun 23, 2026, 02:01 AM UTC
    WAF Scrubbing Region - Azure - EU West (Netherlands)
    Timeline · 4 updates
    • 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.

    • investigating · Jun 20, 2026, 07:32 PM UTC

      We are continuing to investigate this issue.

    • investigating · Jun 20, 2026, 07:48 PM UTC

      We are continuing to investigate this issue.

    • resolved · Jun 23, 2026, 02:01 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. [Service Outage Notice] WAF Scrubbing Region - AWS - US East (Ohio) Scrubbing Servers Down.
    Resolved 1d 9h
    Started Jun 16, 2026, 01:00 PM UTC · Resolved Jun 17, 2026, 10:43 PM UTC
    WAF Scrubbing Region - AWS - US East (Ohio)
    Timeline · 3 updates
    • investigating · Jun 16, 2026, 01:00 PM UTC

      We are currently investigating this issue.

    • monitoring · Jun 17, 2026, 02:41 AM UTC

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

    • 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.

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

  4. [Service Outage Notice] Europe Regions – Azure EU West (Netherlands) Scrubbing Servers Down.
    Resolved 2d 15h
    Started Jun 15, 2026, 07:41 AM UTC · Resolved Jun 17, 2026, 10:43 PM UTC
    WAF Scrubbing Region - Azure - EU West (Netherlands)
    Timeline · 4 updates
    • investigating · Jun 15, 2026, 07:41 AM UTC

      We are currently investigating this issue.

    • 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.

    • 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.

    • 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.

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

  5. [Service Outage Notice] Europe Regions – AWS EU Central (Frankfurt) Scrubbing Servers Down.
    Resolved 2d 15h
    Started Jun 15, 2026, 07:29 AM UTC · Resolved Jun 17, 2026, 10:43 PM UTC
    WAF Scrubbing Region - AWS - EU (Frankfurt)
    Timeline · 9 updates
    • investigating · Jun 15, 2026, 07:29 AM UTC

      We are currently investigating this issue.

    • investigating · Jun 15, 2026, 07:42 AM UTC

      We are continuing to investigate this issue.

    • investigating · Jun 15, 2026, 07:54 AM UTC

      We are continuing to investigate this issue.

    • identified · Jun 15, 2026, 08:55 AM UTC

      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.

    • monitoring · Jun 15, 2026, 02:41 PM UTC

      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.

    • investigating · Jun 16, 2026, 08:39 AM UTC

      We are currently investigating this issue.

    • monitoring · Jun 16, 2026, 12:24 PM UTC

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

    • monitoring · Jun 17, 2026, 11:24 AM UTC

      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).

    • 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.

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

See the full FortiAppSec Cloud outage history

4 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse FortiAppSec Cloud outage history →

Or sign up free to get alerts when FortiAppSec Cloud breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 9 incidents View full outage history →