Whalebone incident

DNS4EU Milan: incorrect DNS responses for some .org domains

Minor Resolved View vendor source →

Whalebone experienced a minor incident on February 21, 2026 affecting DNS4EU and DNS4EU Public resolvers, lasting 114d 5h. The incident has been resolved; the full update timeline is below.

Started
Feb 21, 2026, 02:17 AM UTC
Resolved
Jun 15, 2026, 07:37 AM UTC
Duration
114d 5h
Detected by Pingoru
Feb 21, 2026, 02:17 AM UTC

Affected components

DNS4EUDNS4EU Public resolvers

Update timeline

  1. investigating Feb 21, 2026, 10:24 AM UTC

    We are investigating an issue affecting the DNS4EU public resolver in Milan where some .org domain queries may have returned incorrect DNS responses. As a mitigation, we have removed the affected node from service. We are analyzing logs to determine scope and root cause. Next update in 30 minutes (or sooner).

  2. investigating Feb 21, 2026, 11:04 AM UTC

    Mitigation remains in place (Milan node out of rotation). Service operating normally via remaining resolvers. Investigation into duration/scope/root cause continues. Next update in 60 minutes (or sooner).

  3. investigating Feb 21, 2026, 12:25 PM UTC

    We are preparing to return the Milan DNS4EU resolver node back into service. The node has been checked in isolation and the incorrect .org resolution observed earlier is no longer occurring — DNS queries are resolving correctly now. As a precaution, we have added additional monitoring and alerts so we can quickly detect and respond if the issue happens again. Our investigation is ongoing. Next update will be shared once we have identified the root cause or have more information to share.