Whalebone incident
DNS4EU Milan: incorrect DNS responses for some .org domains
Affected components
Update timeline
- 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).
- 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).
- 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.
Looking to track Whalebone downtime and outages?
Pingoru polls Whalebone's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Whalebone reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Whalebone alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required