Is FortiSandbox down?

Last checked 10m ago
Current status
FortiSandbox is up

No incidents right now.

Official status page: https://status.fortisandboxcloud.forticloud.com · Polled every 5 minutes · 12 components tracked

FortiSandbox is operational right now. Last checked 10m ago; the most recent incident resolved 20h ago.

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

Users who monitor FortiSandbox also follow these Security services: Duo Security LastPass 1Password Barracuda Rapid7 Palo Alto Networks KnowBe4 Incapsula SentinelOne Keeper View all 6,000+ providers
FortiSandbox uptime 100.00% uptime · past 90 days
Mon Wed Fri
MayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 1m
    Started Jul 23, 2026, 05:53 PM UTC · Resolved Jul 23, 2026, 05:55 PM UTC
    Timeline · 2 updates
    • investigating · Jul 23, 2026, 05:53 PM UTC

      Incident for forticare api: Command timed out

    • resolved · Jul 23, 2026, 05:55 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 19m
    Started Jul 11, 2026, 05:19 AM UTC · Resolved Jul 11, 2026, 05:39 AM UTC
    Timeline · 2 updates
    • investigating · Jul 11, 2026, 05:19 AM UTC

      Incident for openstack: Get "https://os.dallas-a.fortistack.corp.fortinet.com:5000/": dial tcp 10.91.64.20:5000: connect: no route to host

    • resolved · Jul 11, 2026, 05:39 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 1h 38m
    Started Jun 24, 2026, 11:57 AM UTC · Resolved Jun 24, 2026, 01:35 PM UTC
    Timeline · 2 updates
    • investigating · Jun 24, 2026, 11:57 AM UTC

      Incident for django health: DatabaseBackend: unavailable: Database error (status code: 500)

    • resolved · Jun 24, 2026, 01:35 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  4. Resolved 13m
    Started May 27, 2026, 03:11 AM UTC · Resolved May 27, 2026, 03:25 AM UTC
    Timeline · 2 updates
    • investigating · May 27, 2026, 03:11 AM UTC

      Incident for django health: MigrationsHealthCheck: unavailable: Database is not ready, DatabaseBackend: unavailable: Database error (status code: 500)

    • resolved · May 27, 2026, 03:25 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved 31m
    Started May 15, 2026, 03:18 AM UTC · Resolved May 15, 2026, 03:49 AM UTC
    Timeline · 2 updates
    • investigating · May 15, 2026, 03:18 AM UTC

      Incident for django health: 404 Not Found 404 Not Found nginx (status code: 404)

    • resolved · May 15, 2026, 03:49 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

Outage history

Past 90 days · 5 incidents View full outage history →
  • Started Jul 23, 2026, 05:53 PM UTC · Resolved Jul 23, 2026, 05:55 PM UTC · 1m
  • Started Jul 11, 2026, 05:19 AM UTC · Resolved Jul 11, 2026, 05:39 AM UTC · 19m
  • Started Jun 24, 2026, 11:57 AM UTC · Resolved Jun 24, 2026, 01:35 PM UTC · 1h 38m
  • Started May 27, 2026, 03:11 AM UTC · Resolved May 27, 2026, 03:25 AM UTC · 13m
  • Started May 15, 2026, 03:18 AM UTC · Resolved May 15, 2026, 03:49 AM UTC · 31m