Whalebone incident

Partial Data Gaps in DNS Traffic Logs

Minor Resolved View vendor source →

Whalebone experienced a minor incident on March 26, 2026 affecting Main region and Log processing and 1 more component, lasting 18h 13m. The incident has been resolved; the full update timeline is below.

Started
Mar 26, 2026, 01:49 PM UTC
Resolved
Mar 27, 2026, 08:02 AM UTC
Duration
18h 13m
Detected by Pingoru
Mar 26, 2026, 01:49 PM UTC

Affected components

Main regionLog processingAPI

Update timeline

  1. investigating Mar 26, 2026, 01:49 PM UTC

    Customers in the Main region may notice intermittent gaps or missing data in the DNS Traffic (PassiveDNS) section of the Whalebone Admin Portal or timeouts when calling API. Affected Services: DNS Traffic dashboards and logs in the portal, API timeouts Unaffected Services: DNS resolution remains fully operational and is not impacted. Other regions are not impacted by this specific issue. We have implemented several infrastructure adjustments to mitigate the impact, and our team is currently working on a permanent fix while continuing to investigate. Next Update: We will provide further information once the permanent fix is deployed and verified. We apologize for any inconvenience this may cause to your services.

  2. monitoring Mar 26, 2026, 03:06 PM UTC

    We identified an issue that temporarily halted the processing of data into our reporting system. Our team has resolved the underlying cause and has resumed data processing. Current Status: The system is currently working through a backlog of information. You will see data appearing in your portal incrementally as the system catches up to real-time. Next Update: We will provide a final confirmation once all reporting and alerting services have returned to real-time operation.

  3. resolved Mar 27, 2026, 08:02 AM UTC

    The issue has been confirmed to be resolved by extended monitoring, and data processing continues in normal operations.