Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

F5 Distributed Cloud Outage History

Every past F5 Distributed Cloud outage tracked by IsDown, with detection times, duration, and resolution details.

There were 323 F5 Distributed Cloud outages since April 2020. The 129 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor May 20, 2026

May 2026: F5 Distributed Cloud - Service Degradation - DNS resolution issue - INC-20260520-462

Detected May 20, 2026 1:01 PM EDT · Resolved May 20, 2026 5:56 PM EDT · Duration about 5 hours

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.

Minor May 11, 2026

May 2026: Incident Advisory:INC-20260511-458

Detected May 11, 2026 9:27 AM EDT · Resolved May 11, 2026 9:51 PM EDT · Duration about 12 hours

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.

Minor May 9, 2026

May 2026: Incident Advisory: INC-20260509-457

Detected May 9, 2026 5:06 PM EDT · Resolved May 10, 2026 2:39 PM EDT · Duration about 22 hours

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.

Minor May 8, 2026

May 2026: F5 Distributed Cloud - Service Interruption - DNS resolution failures - INC-20260508-456

Detected May 8, 2026 3:31 AM EDT · Resolved May 8, 2026 10:06 AM EDT · Duration about 7 hours

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.

Minor May 7, 2026

May 2026: Incident Advisory: INC-20260507-455

Detected May 7, 2026 10:37 AM EDT · Resolved May 7, 2026 10:49 AM EDT · Duration 12 minutes

F5 Distributed Cloud experienced service degradation affecting WAF signature bypass functionality in specific scenarios, with the incident identified on May 7, 2026 at 14:31 UTC. The incident response team was mobilized to investigate the root cause and develop mitigation steps. The issue was resolved after 12 minutes with the team committed to providing detailed incident notifications and updates through their status page.

Minor May 4, 2026

May 2026: Incident Advisory: INC-20260504-454

Detected May 4, 2026 10:37 AM EDT · Resolved May 4, 2026 11:14 PM EDT · Duration about 13 hours

F5 Distributed Cloud experienced delays in their Global Logs Receiver (GLR) service for approximately 12.6 hours. The F5 team identified and mitigated the issue affecting the GLR while other XC Console services remained fully operational throughout the incident. The service was restored and the incident was resolved with continued monitoring to ensure stability.

Minor April 16, 2026

April 2026: Informational: Introduction of New Regional Edge Cluster Chicago (ch2-chi)

Detected Apr 16, 2026 11:07 AM EDT · Resolved Apr 23, 2026 12:39 AM EDT · Duration 7 days

F5 Distributed Cloud launched a new Regional Edge cluster in Chicago (ch2-chi) to enhance redundancy and fault tolerance for their North America infrastructure. The new cluster went live on April 23, 2026 at 4:00 AM UTC, providing improved failover capabilities and better workload distribution across the regional network. This was a planned infrastructure expansion rather than an incident, aimed at strengthening service reliability and availability.

Minor April 11, 2026

April 2026: F5 Distributed Cloud - Service Degradation - Delay in GLR logs - INC-20260411-451

Detected Apr 11, 2026 7:51 PM EDT · Resolved Apr 12, 2026 11:10 AM EDT · Duration about 15 hours

F5 Distributed Cloud experienced delays in Global Log Receiver (GLR) log streaming and access log visibility in the console for 15.3 hours. Core services and traffic flow remained fully operational throughout the incident, with only log streaming affected. The issue was resolved with live log visibility restored and all delayed logs successfully backfilled.

Minor April 7, 2026

April 2026: Informational: Introduction of New Regional Edge Cluster Atlanta (At1-atl)

Detected Apr 7, 2026 11:21 PM EDT · Resolved Apr 16, 2026 11:03 AM EDT · Duration 8 days

F5 Distributed Cloud launched a new Regional Edge cluster in Atlanta (At1-atl) to enhance redundancy and fault tolerance across their North America infrastructure. The new cluster went live on April 16, 2026 at 4:00 AM UTC, improving failover capabilities and traffic management for users in the region. The deployment was successfully completed as scheduled with no service disruptions reported.

Minor April 6, 2026

April 2026: F5 Distributed Cloud - Service Degradation - DNS resolution failures for CDN domain - INC-20260406-450

Detected Apr 6, 2026 10:49 AM EDT · Resolved Apr 7, 2026 3:43 AM EDT · Duration about 17 hours

F5 Distributed Cloud experienced intermittent DNS resolution failures affecting CDN traffic in the European region for 16.9 hours. The issue was caused by connectivity failures that prevented customers from reaching certain endpoints or services relying on DNS lookups. The team implemented a workaround to stabilize services and later applied a permanent resolution, with all services returning to normal operation.