F5 Distributed Cloud Outage History

F5 Distributed Cloud experienced a 31.5-hour service degradation where customers encountered delays in Global Log Receiver (GLR) log streaming, affecting their ability to access and audit platform activities in real-time. Core XC Console services and traffic flow remained fully operational throughout the incident. The issue was identified and resolved with both live logs and backfill logs restored to normal operations.

F5 Distributed Cloud experienced service degradation affecting the Global Logs Receiver (GLR) component, impacting log processing functionality while core console services and traffic remained operational. The incident lasted 12.2 hours, beginning at 2:52 PM UTC on June 8th, 2026, and was fully resolved by 3:07 AM UTC on June 9th, 2026.

F5 Bot Defense experienced service degradation for 20.7 hours after a scheduled maintenance window on June 6th, 2026, caused by false positives in rate-limiting policies that incorrectly blocked legitimate traffic. The issue affected the shared rate limiter component, leading to performance problems for users relying on bot protection services. The F5 team resolved the rate-limiting policy issues and restored normal service functionality by June 7th at 18:00 UTC.

F5 Distributed Cloud experienced service degradation affecting GLR log streaming for 42 minutes. The incident impacted GLR logs functionality, potentially affecting customer operations. The F5 team successfully resolved the issue and confirmed the system returned to normal operation.

F5 Distributed Cloud experienced service degradation affecting synthetic monitoring functionality for 4.8 hours, while core XC Console services remained fully operational throughout the incident. The issue was identified at 20:00 UTC, with the team implementing a fix and recovering services by 22:45 UTC before fully resolving the incident at 00:55 UTC the following day.

F5 Distributed Cloud experienced a 27.4-hour service degradation affecting CDN edge nodes, causing intermittent traffic disruptions and increased latency as traffic was rerouted to healthy nodes. The incident impacted the CDN Control Plane and CDN capabilities, with customers experiencing performance issues during the outage period. The issue was identified and corrective measures were implemented, with all CDN services and nodes returning to full operational status.

F5 Distributed Cloud experienced DNS resolution issues that caused service degradation and intermittent DNS resolution failures for customers using F5 DNS services. The incident began around 16:25 UTC on May 20, 2026, and affected DNS availability and operations for impacted customers. The engineering team implemented corrective measures and fully resolved the issue after 4.9 hours, with all services returning to normal operation and ongoing monitoring to ensure stability.

F5 Distributed Cloud experienced service degradation affecting their internal DNS zone, which impacted customer operations for 12.4 hours. The incident was identified at 01:21 PM UTC on May 11th, 2026, and the incident response team was mobilized to investigate and assess the impact. The issue was successfully resolved by 01:48 AM UTC on May 12th, 2026, with the system returning to normal operations.

F5 Distributed Cloud experienced delays in CDN configuration propagation across multiple regions for approximately 21.6 hours, starting on May 9, 2026 at 20:55 UTC. The incident affected CDN deployment configurations but did not impact customer traffic. The issue was resolved on May 10, 2026 at 18:36 UTC after remediation actions restored normal configuration propagation behavior across all affected regions.

F5 Distributed Cloud experienced intermittent DNS resolution failures across multiple regions for 6.6 hours, causing customers to occasionally fail when attempting to reach certain endpoints or services that rely on DNS lookups. The engineering team identified the root cause and implemented a fix, with the issue fully resolved and all services restored to normal operation.