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 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.

The FortiAnalyzer service experienced a minor outage due to FortiCare API command timeouts. The incident affected automated outage detection functionality for 9 minutes. The issue was resolved after investigation and monitoring confirmed service restoration.

FortiAnalyzer experienced a major network incident that affected the FortiAnalyzer Cloud Portal for 35 minutes. The service team investigated the issue and successfully resolved it. All affected portal components were restored to normal operation.

FortiAnalyzer's FortiCare API experienced command timeouts, causing a minor service disruption. The incident was automatically detected and affected API functionality for approximately 5 minutes. The service was restored and the incident was resolved within the same timeframe.

FortiAnalyzer's health check endpoint in the ca-west-1 region experienced connectivity issues, with requests timing out when attempting to reach the service at 160.223.172.24:443. The outage lasted 14.3 hours before being resolved. The incident was classified as minor and has been fully restored.

FortiAnalyzer experienced connectivity issues with the OpenStack authentication service in the Tokyo-A region, resulting in timeout errors when attempting to authenticate API requests. The incident affected automated systems' ability to obtain authentication tokens from the OpenStack service. The connectivity issue was resolved after 7 minutes of investigation.

FortiAnalyzer experienced a minor outage due to connection failures when attempting to authenticate with the OpenStack service in Dallas, with requests being refused at the TCP level. The incident affected automated systems trying to obtain authentication tokens from the OpenStack API. The issue was resolved after 6 minutes of investigation.