NORTHFLANK · Vendor
NO FIX YET
Northflank reported a DDoS attack against its US-Central region that affected public ingress into clusters while internal traffic stayed up. The incident was marked resolved after about 2 hours and 49 minutes, with mitigations in place.
first public Jul 21, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Customers whose public services ran on Northflank clusters in the US-Central region during the attack window on July 21 were likely affected by reduced public reachability. Internal cluster traffic was not affected, and the sources describe no customer-side vulnerability or action to take.
Not affected if internal-only-services, other-regions
Who cares kubernetes, northflank, security, self-hosted
No fix yet, per the sources.
Type: Incident Duration: 2 hours and 49 minutes
Affected Components: Networking
Jul 21, 13:58:28 GMT+0 - Resolved - This incident has been resolved. We will continue to monitor the affected region. Jul 21, 13:43:46 GMT+0 - Monitoring - We have implemented mitigations are monitoring the situation. Jul 21, 13:23:09 GMT+0 - Identified - We are currently experiencing a DDoS attack in the US - Central region. This is affecting public ingress into the cluster. Internal traffic is not affected. The team is working on additional mitigations. Jul 21, 11:41:41 GMT+0 - Resolved - The DDoS attack has stopped, we will continue to monitor the affected region. Jul 21, 11:: GMT+ - Monitoring - We have implemented mitigations are monitoring the situation. Jul , :: GMT+ - Identified - We are currently experiencing a DDoS attack the US - Central region. This affecting ingress the cluster. Internal traffic affected. The team working additional mitigations.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.