FortiAnalyzer Outage History

FortiAnalyzer experienced a database connectivity issue that caused the Django health checks to fail with 500 status codes, affecting the DatabaseBackend and MigrationsHealthCheck components. The incident lasted 8 minutes and was automatically detected by the monitoring system. The service was restored and the incident was resolved without requiring manual intervention.

FortiAnalyzer experienced a 7.3-hour outage due to OpenStack authentication service connectivity issues, with connection attempts to the authentication endpoint being refused. The incident affected automated systems that rely on OpenStack authentication tokens. The service was restored and the incident was resolved.

FortiAnalyzer experienced a database connectivity issue that caused health check failures and prevented the service from functioning properly. The incident affected the database backend and migration systems, resulting in 500 status code errors. The service was restored after 47 minutes when the database connectivity was resolved.

FortiAnalyzer experienced a database connectivity issue that caused the Django health checks to fail with 500 status codes, indicating the database backend was unavailable and migrations could not be completed. The incident lasted 16 minutes and was automatically detected by the monitoring system. The service was restored after the database connectivity was resolved.

FortiAnalyzer experienced a database connectivity issue that caused the Django health checks to fail with 500 status codes, affecting the DatabaseBackend and MigrationsHealthCheck components. The incident was automatically detected and lasted approximately 6 minutes before being resolved. The service has been restored to normal operation.

A power outage at the San Jose data center caused a major incident affecting FortiAnalyzer services for 3.4 hours. The incident was resolved after power was restored to the facility. No specific details about service impact or resolution steps were provided in the incident updates.

FortiAnalyzer experienced a database connectivity issue that caused the Django health checks to fail with 500 status codes, affecting the DatabaseBackend and MigrationsHealthCheck components. The incident lasted 4 minutes and was automatically detected by the monitoring system. The service was restored and the incident was resolved without requiring manual intervention.

FortiAnalyzer experienced a 5-minute server outage with automated detection triggering due to a 504 gateway timeout error that prevented access to the service. The incident was automatically detected and resolved within approximately 2 minutes of initial reporting.

The FortiAnalyzer FortiStack Platform in the us-central-1 region experienced a major outage lasting 1 hour. The incident affected the FAZFMG service availability in that region. The issue was resolved after investigation and service was restored.

FortiAnalyzer experienced a major service incident during network maintenance that lasted 2.7 hours. The incident was resolved after investigation and remediation efforts. Service was fully restored and the incident was marked as resolved.