FortiAnalyzer Outage History

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.

FortiAnalyzer's automated health monitoring system experienced connectivity issues, with health check requests to the ca-west-1 region failing due to TCP connection timeouts. The outage affected the service's ability to perform automated health checks for approximately 7 days. The incident was detected through automated monitoring and is currently under investigation.

FortiAnalyzer experienced an internal server error that affected OpenStack functionality for 18 minutes. The incident was resolved after investigation and troubleshooting. Service was restored to normal operation.

FortiAnalyzer experienced network instability that affected the Cloud Portal for 7 minutes. The service team investigated the issue and successfully resolved it. The incident impacted users' ability to access the FortiAnalyzer Cloud Portal during this brief outage.

FortiAnalyzer experienced a connectivity issue where OpenStack authentication requests to the corporate server failed due to network routing problems, preventing access to authentication tokens. The incident lasted 9 minutes and was resolved without further details on the specific fix implemented.