FortiSOAR Outage History
FortiSOAR is up right nowPingoru has recorded 40 incidents for FortiSOAR: 30 in the last 12 months and 22 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 5 | 2 of 744 (0%) |
| August 2026 | 8 | 6 of 744 (1%) |
| September 2026 | 6 | 1 of 720 (0%) |
| October 2026 | 7 | 24 of 508 (5%) |
Incidents, newest first
Notice October 21, 2026 Automated Recovery 2m
Started Oct 21, 2026, 06:04 AM UTC· resolved Oct 21, 2026, 06:06 AM UTC
- investigating Oct 21, 2026, 06:04 AM UTC
Incident for django health: The page is temporarily unavailable /**/ nginx error! The page you are looking for is temporarily unavailable. Please try again later. Website Administrator Something has triggered an error on your website. This is the default error page for nginx that is distributed with Fedora. It is located /usr/share/nginx/html/50x.html You should customize this error page for your own site or edit the error_page directive in the nginx configuration file /etc/nginx/nginx.conf. (status code: 502)
- resolved Oct 21, 2026, 06:06 AM UTC
This incident has been resolved.
Notice August 25, 2026 Automated Outage Detection 4m
Started Aug 25, 2026, 08:46 PM UTC· resolved Aug 25, 2026, 08:51 PM UTC
- 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
- resolved Aug 25, 2026, 08:51 PM UTC
This incident has been resolved.
Major August 18, 2026 FortiSOAR Cloud Global Network Latency Incident 1h 31m FortiSOAR Cloud Portal, FortiSOAR Cloud Portal, FortiSOAR Cloud Portal, FortiSOAR Cloud Portal and 1 more
Started Aug 18, 2026, 11:25 AM UTC· resolved Aug 18, 2026, 12:57 PM UTC
- investigating Aug 18, 2026, 11:25 AM UTC
We are currently investigating this issue.
- resolved Aug 18, 2026, 12:57 PM UTC
This incident has been resolved.
Major December 17, 2025 Plano DC Internet Flapping 21m FortiSOAR Cloud Portal
Started Dec 17, 2025, 01:15 AM UTC· resolved Dec 17, 2025, 01:37 AM UTC
- investigating Dec 17, 2025, 06:07 PM UTC
We are currently investigating this issue.
- resolved Dec 17, 2025, 06:08 PM UTC
This incident has been resolved.
Notice December 15, 2025 Provision failure on cloud portal 27m FortiSOAR Cloud Portal, FortiSOAR Cloud Portal, FortiSOAR Cloud Portal
Started Dec 15, 2025, 06:37 PM UTC· resolved Dec 15, 2025, 07:04 PM UTC
- investigating Dec 15, 2025, 06:37 PM UTC
The new instance can not be provisioned during the maintenance window.
- resolved Dec 15, 2025, 07:04 PM UTC
This incident has been resolved.
Critical November 12, 2025 FortiSOAR Cloud control-plane issue 1h 45m FortiSOAR Cloud Portal
Started Nov 12, 2025, 10:45 PM UTC· resolved Nov 13, 2025, 12:30 AM UTC
- investigating Nov 13, 2025, 01:23 AM UTC
We are currently investigating this issue.
- resolved Nov 13, 2025, 01:23 AM UTC
This incident has been resolved.
Notice October 21, 2025 facility issue in Plano DC 5h FortiSOAR Cloud Portal, FortiStack
Started Oct 21, 2025, 12:30 PM UTC· resolved Oct 21, 2025, 05:30 PM UTC
- investigating Oct 21, 2025, 01:52 PM UTC
We are currently investigating this issue.
- resolved Oct 21, 2025, 04:06 PM UTC
This incident has been resolved.
Notice August 29, 2025 There is currently an issue at backend on US and the team is investigating. 13h 15m FortiSOAR Cloud Portal
Started Aug 29, 2025, 03:30 AM UTC· resolved Aug 29, 2025, 04:45 PM UTC
- investigating Aug 29, 2025, 07:55 AM UTC
We are currently investigating this issue.
- resolved Aug 29, 2025, 04:45 PM UTC
This incident has been resolved.
Notice January 17, 2025 DNS issue 35m FortiSOAR Cloud Portal, FortiSOAR Cloud Portal, FortiSOAR Cloud Portal, Forticare Service and 5 more
Started Jan 17, 2025, 07:13 AM UTC· resolved Jan 17, 2025, 07:48 AM UTC
- 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.
- resolved Jan 17, 2025, 07:48 AM UTC
This incident has been resolved.