FortiSandbox Outage History

FortiSandbox is up right now

FortiSandbox had 14 outages in the last 2 years totaling 87h 44m of downtime, averaging 0.6 incidents per month.

There were 14 FortiSandbox outages since November 13, 2024 totaling 87h 44m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.fortisandboxcloud.forticloud.com

Major October 19, 2026

FortiSandbox Cloud PaaS Storage performance incident

Detected by Pingoru
Oct 19, 2026, 11:06 AM UTC
Resolved
Oct 19, 2026, 11:55 PM UTC
Duration
12h 48m
Affected: FortiSandbox Cloud PortalFortiStack
Timeline · 2 updates
  1. investigating Oct 19, 2026, 11:06 AM UTC

    We are currently investigating this issue.

  2. resolved Oct 19, 2026, 11:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 19, 2026

Automated Recovery

Detected by Pingoru
Oct 19, 2026, 08:57 AM UTC
Resolved
Oct 19, 2026, 08:59 AM UTC
Duration
2m
Timeline · 2 updates
  1. investigating Oct 19, 2026, 08:57 AM UTC

    Incident for django health: Server Error (500) Server Error (500) (status code: 500)

  2. resolved Oct 19, 2026, 08:59 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 18, 2026

FortiStack platform issue

Detected by Pingoru
Mar 18, 2026, 03:30 AM UTC
Resolved
Mar 18, 2026, 06:00 PM UTC
Duration
14h 30m
Affected: FortiSandbox Cloud PortalFortiStack
Timeline · 2 updates
  1. investigating Mar 18, 2026, 06:18 PM UTC

    We are currently investigating this issue.

  2. resolved Mar 18, 2026, 06:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 10, 2026

network unstable

Detected by Pingoru
Mar 10, 2026, 06:34 PM UTC
Resolved
Mar 10, 2026, 06:42 PM UTC
Duration
8m
Affected: FortiSandbox Cloud Portal
Timeline · 2 updates
  1. investigating Mar 11, 2026, 07:03 PM UTC

    We are currently investigating this issue.

  2. resolved Mar 11, 2026, 07:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 10, 2026

March 2026: FortiSandbox incident

Detected by Pingoru
Mar 10, 2026, 06:34 PM UTC
Resolved
Mar 10, 2026, 06:42 PM UTC
Duration
8m
Timeline · 2 updates
  1. investigating Mar 10, 2026, 06:34 PM UTC

    Incident for openstack: Post "https://FRN-pr-vn-01.corp.fortinet.com:5000/v3/auth/tokens": dial tcp 10.78.5.2:5000: connect: no route to host

  2. resolved Mar 10, 2026, 06:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical February 9, 2026

FortiSandbox Cloud PaaS ca-west-1 Region Down

Detected by Pingoru
Feb 09, 2026, 07:40 AM UTC
Resolved
Feb 09, 2026, 03:20 PM UTC
Duration
7h 40m
Affected: FortiSandbox Cloud Portal
Timeline · 2 updates
  1. investigating Feb 09, 2026, 04:05 PM UTC

    We are currently investigating this issue.

  2. resolved Feb 09, 2026, 04:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 8, 2026

network maintenance

Detected by Pingoru
Feb 08, 2026, 09:00 AM UTC
Resolved
Feb 09, 2026, 02:39 AM UTC
Duration
17h 39m
Affected: FortiSandbox Cloud PortalFortiStack
Timeline · 5 updates
  1. investigating Feb 09, 2026, 02:16 AM UTC

    We are currently investigating this issue.

  2. investigating Feb 09, 2026, 02:25 AM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 09, 2026, 02:26 AM UTC

    We are continuing to investigate this issue.

  4. investigating Feb 09, 2026, 02:27 AM UTC

    We are continuing to investigate this issue.

  5. resolved Feb 09, 2026, 02:39 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 18, 2025

ISP Network Unstable

Detected by Pingoru
Dec 18, 2025, 08:15 AM UTC
Resolved
Dec 18, 2025, 01:45 PM UTC
Duration
5h 30m
Affected: FortiSandbox Cloud Portal
Timeline · 2 updates
  1. investigating Dec 18, 2025, 06:46 PM UTC

    ISP network is unstable during the incident period, some customers may experienced latency and connection lost issue.

  2. resolved Dec 18, 2025, 06:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 17, 2025

Plano DC Internet Flapping

Detected by Pingoru
Dec 17, 2025, 01:15 AM UTC
Resolved
Dec 17, 2025, 01:37 AM UTC
Duration
22m
Affected: FortiSandbox Cloud Portal
Timeline · 2 updates
  1. investigating Dec 17, 2025, 06:18 PM UTC

    We are currently investigating this issue.

  2. resolved Dec 17, 2025, 06:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 12, 2025

FortiSandbox Cloud control-plane issue

Detected by Pingoru
Nov 12, 2025, 10:45 PM UTC
Resolved
Nov 13, 2025, 12:30 AM UTC
Duration
1h 45m
Affected: FortiSandbox Cloud PortalFortiSandbox Cloud PortalFortiSandbox Cloud Portal
Timeline · 2 updates
  1. investigating Nov 13, 2025, 01:16 AM UTC

    We are currently investigating this issue.

  2. resolved Nov 13, 2025, 01:16 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 21, 2025

facility issue in Plano DC

Detected by Pingoru
Oct 21, 2025, 12:30 PM UTC
Resolved
Oct 21, 2025, 05:30 PM UTC
Duration
4h 59m
Affected: FortiSandbox Cloud PortalFortiStack
Timeline · 2 updates
  1. investigating Oct 21, 2025, 01:51 PM UTC

    We are currently investigating this issue.

  2. resolved Oct 21, 2025, 04:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 17, 2025

DNS issue

Detected by Pingoru
Jan 17, 2025, 07:12 AM UTC
Resolved
Jan 17, 2025, 07:48 AM UTC
Duration
35m
Affected: FortiSandbox Cloud PortalFortiSandbox Cloud PortalFortiSandbox Cloud PortalForticare ServiceForticare ServiceForticare ServiceFortiStackFortiStackFortiStack
Timeline · 2 updates
  1. investigating Jan 17, 2025, 07:12 AM UTC

    We are currently experiencing a DNS issue. Our team is actively investigating the root cause, and we sincerely apologize for any inconvenience this may cause. We will provide regular updates as we work toward a resolution.

  2. resolved Jan 17, 2025, 07:48 AM UTC

    This incident has been resolved.

Read the full incident report →