F5 incident
F5 Distributed Cloud - Service Interruption - Issue with DNSSEC - INC-20260108-426
F5 experienced a major incident on January 8, 2026 affecting DNS, lasting 4h 2m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 08, 2026, 08:55 AM UTC
This advisory is to inform you that we are currently investigating reports of service degradation affecting DNSSEC in multiple regions. 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 01/08/2026, 08: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.
- monitoring Jan 08, 2026, 09:45 AM UTC
The F5 Distributed Cloud support team identified an issue with the DNSSEC feature that impacted responses from the resolver. The recent DNS changes have been reverted, which has mitigated the impact, and the issue is now nearing full resolution. Our team is actively monitoring the situation and continuing to work toward a complete fix. We appreciate your patience and will keep you informed with any further updates. Thank you for your understanding.
- resolved Jan 08, 2026, 12:57 PM UTC
The issue with F5 Distributed Cloud affecting the DNSSEC feature, which impacted responses from the resolver, has been resolved and is now fully operational. All other services remained fully operational throughout the incident. This incident has been marked as resolved.