Is FortiAppSec Cloud down?

Last checked 7m ago
Current status
FortiAppSec Cloud is up

No incidents right now.

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

FortiAppSec Cloud is operational right now. Last checked 7m ago; the most recent incident resolved 2d 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 5 incidents in the last 90 days (99.77% 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.77% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 1h 17m
    Started Jun 12, 2026, 09:38 AM UTC · Resolved Jun 12, 2026, 10:55 AM UTC
    WAF Scrubbing Region - Azure - EU West (Netherlands)
    Timeline · 5 updates
    • investigating · Jun 12, 2026, 09:38 AM UTC

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

    • identified · Jun 12, 2026, 09:52 AM UTC

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

    • monitoring · Jun 12, 2026, 09:58 AM UTC

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

    • monitoring · Jun 12, 2026, 10:00 AM UTC

      We are continuing to monitor for any further issues.

    • resolved · Jun 12, 2026, 10:55 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 6d 15h
    Started May 19, 2026, 02:03 AM UTC · Resolved May 25, 2026, 05:10 PM UTC
    WAF Scrubbing Region - AWS - US East (Ohio)WAF Scrubbing Region - AWS - US East (N. Virginia)
    Timeline · 8 updates
    • 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.

    • investigating · May 19, 2026, 02:05 AM UTC

      We are continuing to investigate this issue.

    • investigating · May 19, 2026, 02:35 AM UTC

      We are continuing to investigate this issue.

    • investigating · May 19, 2026, 03:49 AM UTC

      We are continuing to investigate this issue.

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

    • identified · May 19, 2026, 04:12 AM UTC

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

    • monitoring · May 19, 2026, 05:17 AM UTC

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

    • resolved · May 25, 2026, 05:10 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 3h 34m
    Started May 13, 2026, 09:52 PM UTC · Resolved May 14, 2026, 01:26 AM UTC
    WAF Scrubbing Region - AWS - US East (Ohio)
    Timeline · 2 updates
    • 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.

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

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

Outage history

Past 90 days · 3 incidents View full outage history →