Whalebone incident

Regulatory domains not being blocked in selected regions

Minor Resolved View vendor source →

Whalebone experienced a minor incident on January 17, 2026 affecting Main region and EU-01 and 1 more component, lasting 5d 18h. The incident has been resolved; the full update timeline is below.

Started
Jan 17, 2026, 07:00 PM UTC
Resolved
Jan 23, 2026, 01:58 PM UTC
Duration
5d 18h
Detected by Pingoru
Jan 17, 2026, 07:00 PM UTC

Affected components

Main regionEU-01APAC-01AM-01On-Prem resolversAdmin PortalRegulatory listsAdmin Portal

Update timeline

  1. investigating Jan 23, 2026, 08:52 AM UTC

    We have identified an issue where selected regulatory domains—primarily in the Czechia and Poland regions—that should be blocked based on regulatory feeds are currently not being blocked. We are actively investigating the affected domains and whether other regulatory lists or regions may also be impacted. Impact Regulatory domains that should be blocked may still resolve normally for some customers. Other DNS resolution and protection services remain operational. What We’re Doing Our engineering and operations teams are actively investigating the underlying cause of this enforcement gap. We are reviewing the regulatory list propagation and enforcement logic across resolver regions. Next Update We expect to provide the next update as soon as new information becomes available.

  2. resolved Jan 23, 2026, 01:58 PM UTC

    The incident has been resolved, and all regulatory lists are now correctly propagated and enforced on the resolvers. We are currently identifying the root cause and defining measures to prevent similar issues in the future. We apologize for any inconvenience caused.