FortiSOAR Outage History

FortiSOAR is up right now

FortiSOAR had 9 outages in the last 2 years totaling 46h 19m of downtime — averaging 0.4 incidents per month.

There were 9 FortiSOAR outages since January 17, 2025 totaling 46h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.fortisoar.forticloud.com

Notice October 11, 2026

Automated Recovery

Detected by Pingoru
Oct 11, 2026, 12:04 AM UTC
Resolved
Oct 11, 2026, 11:22 PM UTC
Duration
23h 18m
Timeline · 2 updates
  1. investigating Oct 11, 2026, 12:04 AM UTC

    Incident for openstack: The service is currently unable to handle the request due to a temporary overloading or maintenance. This is a temporary condition. Try again later.

  2. resolved Oct 11, 2026, 11:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 25, 2026

Automated Outage Detection

Detected by Pingoru
Aug 25, 2026, 08:46 PM UTC
Resolved
Aug 25, 2026, 08:51 PM UTC
Duration
4m
Timeline · 2 updates
  1. investigating Aug 25, 2026, 08:46 PM UTC

    Incident for django health: failed to execute request: Get "https://eu-central-2.fortisoar.forticloud.com/health-check?format=json": dial tcp 189.25.42.3:443: i/o timeout

  2. resolved Aug 25, 2026, 08:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 18, 2026

FortiSOAR Cloud Global Network Latency Incident

Detected by Pingoru
Aug 18, 2026, 11:25 AM UTC
Resolved
Aug 18, 2026, 12:57 PM UTC
Duration
1h 31m
Affected: FortiSOAR Cloud PortalFortiSOAR Cloud PortalFortiSOAR Cloud PortalFortiSOAR Cloud PortalFortiSOAR Cloud Portal
Timeline · 2 updates
  1. investigating Aug 18, 2026, 11:25 AM UTC

    We are currently investigating this issue.

  2. resolved Aug 18, 2026, 12:57 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
21m
Affected: FortiSOAR Cloud Portal
Timeline · 2 updates
  1. investigating Dec 17, 2025, 06:07 PM UTC

    We are currently investigating this issue.

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

    This incident has been resolved.

Read the full incident report →

Notice December 15, 2025

Provision failure on cloud portal

Detected by Pingoru
Dec 15, 2025, 06:37 PM UTC
Resolved
Dec 15, 2025, 07:04 PM UTC
Duration
27m
Affected: FortiSOAR Cloud PortalFortiSOAR Cloud PortalFortiSOAR Cloud Portal
Timeline · 2 updates
  1. investigating Dec 15, 2025, 06:37 PM UTC

    The new instance can not be provisioned during the maintenance window.

  2. resolved Dec 15, 2025, 07:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 12, 2025

FortiSOAR 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: FortiSOAR Cloud Portal
Timeline · 2 updates
  1. investigating Nov 13, 2025, 01:23 AM UTC

    We are currently investigating this issue.

  2. resolved Nov 13, 2025, 01:23 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
5h
Affected: FortiSOAR Cloud PortalFortiStack
Timeline · 2 updates
  1. investigating Oct 21, 2025, 01:52 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:13 AM UTC
Resolved
Jan 17, 2025, 07:48 AM UTC
Duration
35m
Affected: FortiSOAR Cloud PortalFortiSOAR Cloud PortalFortiSOAR Cloud PortalForticare ServiceForticare ServiceForticare ServiceFortiStackFortiStackFortiStack
Timeline · 2 updates
  1. investigating Jan 17, 2025, 07:13 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 →