Partial DNS, Threats, and Content Logs Processing Loss in EU-01 Region

After the investigation we have revealed the log data are not lost and all of them are preserved. Update on April 24th disclosed the fact some logs were accidentally duplicated. Log counts have now been normalized, and processing is back to expected levels. A permanent fix will be implemented to prevent future duplications.

This incident is now considered as invalid and resolved. Thank you for your patience and apologies for any confusion caused.

We’ve validated several hypotheses such as infrastructure changes, capacity adjustments, log routing, and client-specific factors, but none fully explain the reduction in logs processing. Investigation is ongoing and we’ll share our next update tomorrow, April 29.
Thank you for your patience.

We have detected an issue causing a reduction in processing of DNS traffic, Threats logs, and Content logs for some customers in the EU‑01 region. The incident began on Friday, April 24, 2025 at approximately 07:49 UTC+2, immediately after an infrastructure update enforcing TLS 1.3.

Initial rollback actions partially restored the traffic, but further analysis indicates an ongoing impact, with approximately 30% of logs not being processed as expected.

We are actively investigating the root cause, suspecting potential issues related to rate limiting or infrastructure bottlenecks.

Further updates will be provided as we progress. We apologize for any inconvenience caused and appreciate your patience.