FortiManager Cloud Service logo and current status indicator

FortiManager Cloud Service Incident History

FortiManager Cloud Service is currently operational with all systems functioning normally.

Last checked Jul 26, 2026 4:39 PM UTC from FortiManager Cloud Service's official status page

Incident History

Showing incidents from the last 15 days

Report: "Automated Recovery"

Last update
resolved

This incident has been resolved.

investigating

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.

Report: "Automated Recovery"

Last update
resolved

This incident has been resolved.

investigating

Incident for openstack: Post "https://os.sanjose-a.fortistack.corp.fortinet.com:5000/v3/auth/tokens": net/http: TLS handshake timeout

Report: "Automated Recovery"

Last update
resolved

This incident has been resolved.

investigating

Incident for openstack: Expected HTTP response code [201 202] when accessing [POST https://os.sanjose-a.fortistack.corp.fortinet.com:5000/v3/auth/tokens], but got 504 instead <html><body><h1>504 Gateway Time-out</h1> The server didn't respond in time. </body></html>

Report: "Automated Recovery"

Last update
resolved

This incident has been resolved.

investigating

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.

Report: "Automated Recovery"

Last update
resolved

This incident has been resolved.

investigating

Incident for openstack: Internal Server Error

Report: "Automated Outage Detection"

Last update
investigating

Incident for django health: <!doctype html> <html lang="en"> <head> <title>Server Error (500)</title> </head> <body> <h1>Server Error (500)</h1><p></p> </body> </html> (status code: 500)

Report: "Automated Outage Detection"

Last update
investigating

Incident for django health: <!doctype html> <html lang="en"> <head> <title>Server Error (500)</title> </head> <body> <h1>Server Error (500)</h1><p></p> </body> </html> (status code: 500)

Report: "Automated Outage Detection"

Last update
investigating

Incident for django health: <!doctype html> <html lang="en"> <head> <title>Server Error (500)</title> </head> <body> <h1>Server Error (500)</h1><p></p> </body> </html> (status code: 500)

Report: "Automated Outage Detection"

Last update
resolved

This incident has been resolved.

investigating

Incident for django health: <!doctype html> <html lang="en"> <head> <title>Server Error (500)</title> </head> <body> <h1>Server Error (500)</h1><p></p> </body> </html> (status code: 500)

Report: "Automated Outage Detection"

Last update
investigating

Incident for django health: Cache(alias='default'): OK, Database(alias='default'): OK, Storage(alias='default'): OK, Redis(db=0, host='10.73.15.200', port=6379): OK (status code: 200)

Report: "Automated Outage Detection"

Last update
investigating

Incident for django health: <!doctype html> <html lang="en"> <head> <title>Server Error (500)</title> </head> <body> <h1>Server Error (500)</h1><p></p> </body> </html> (status code: 500)

Report: "Automated Outage Detection"

Last update
investigating

Incident for django health: Cache(alias='default'): OK, Database(alias='default'): OK, Storage(alias='default'): OK, Redis(db=0, host='10.15.0.100', port=6379): OK (status code: 200)

Report: "Automated Outage Detection"

Last update
investigating

Incident for django health: Cache(alias='default'): OK, Database(alias='default'): OK, Storage(alias='default'): OK, Redis(db=0, host='10.15.0.200', port=6379): OK (status code: 200)