Is FortiAppSec Cloud down?

Last checked just now
Current status
FortiAppSec Cloud is up

No incidents right now.

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

FortiAppSec Cloud is operational right now. Last checked just now; the most recent incident resolved 17d 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 46 FortiAppSec Cloud services and has captured 5 incidents in the last 90 days (99.76% 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.76% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. 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. 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.

Outage history

Past 90 days · 2 incidents View full outage history →