F5 incident

F5 Distributed Cloud -Service Degradation-DNS resolution issue-INC-20260913-513

Minor Resolved View vendor source →

F5 experienced a minor incident on September 13, 2026 affecting DNS, lasting 16h 41m. The incident has been resolved; the full update timeline is below.

Started
Sep 13, 2026, 10:55 AM UTC
Resolved
Sep 14, 2026, 03:36 AM UTC
Duration
16h 41m
Detected by Pingoru
Sep 13, 2026, 10:55 AM UTC

Affected components

DNS

Update timeline

  1. investigating Sep 13, 2026, 10:55 AM UTC

    This advisory is to inform you that we are currently investigating reports of service degradation affecting DNS services We understand this may be affecting your operations and we are committed to providing transparent and timely updates as more information becomes available. While we gather more information, we recommend monitoring the progress on this site (https://www.f5cloudstatus.com/) for the latest update. Investigation Status: • We have identified potential service impact at 10:50 UTC; • Our incident response team has been fully mobilized; • Initial investigation and impact assessment efforts are underway. Next Steps: • A detailed incident notification will be provided within 30 minutes; • Our teams are working to determine the root cause of the incident; • We will share mitigation steps as soon as they become available. We appreciate your patience as we work to resolve this situation. If you are experiencing a critical business impact, please contact our support team through your established channels. Thank you for your continued support and trust in F5.

  2. investigating Sep 13, 2026, 12:26 PM UTC

    The F5 Distributed Cloud team is actively investigating a managed DNS service issue affecting certain Load Balancer configurations. No further customer impact is currently being observed for configurations utilizing Internet (Specified VIP) and Virtual Site (Specified VIP). Our engineering team is proactively analyzing the environment to isolate the cause and ensure ongoing system stability. Thank you for your patience.

  3. identified Sep 13, 2026, 01:26 PM UTC

    The F5 Distributed Cloud team has identified the cause of the managed DNS service issue. The issue was caused by a change to the DNS configuration introduced with the Distributed Cloud 8.0 release. Our Engineering teams are actively monitoring the environment, and no further customer impact is currently being observed. We will share further updates as more information becomes available.Thank you for your patience.

  4. identified Sep 13, 2026, 05:27 PM UTC

    The F5 Distributed Cloud team continues working on the hotfix for the issue caused by a DNS configuration change. Our Engineering teams are actively working to fully recover the DNS service. We will share further updates as more information becomes available.

  5. identified Sep 13, 2026, 09:22 PM UTC

    The F5 Distributed Cloud team is now testing and validating the hotfix for the issue caused by a DNS configuration change, to ensure system stability. We will share further updates as more information becomes available.

  6. resolved Sep 14, 2026, 03:36 AM UTC

    The F5 Distributed Cloud team has successfully deployed the hotfix addressing the managed DNS service issue. DNS services have been restored to normal operation. Our engineering teams are continuously monitoring telemetry and service health to ensure sustained stability. Thank you for your patience and understanding while we worked to resolve this issue. Sincerely, F5 Distributed Cloud