CyberFOX incident

[DNS] Investigating issue - Resolution Issues with Latest Version

CyberFOX experienced a minor incident on April 18, 2026 affecting Resolver (us-east-1, us-west-2, eu-west-2, ap-southeast-2) and Upstream (us-east-1, us-west-2, eu-west-2, ap-southeast-2), lasting —. The incident has been resolved; the full update timeline is below.

Started: Apr 18, 2026, 08:23 AM UTC
Resolved: Apr 17, 2026, 08:23 AM UTC
Duration: —
Detected by Pingoru: Apr 18, 2026, 08:23 AM UTC

Affected components

Resolver (us-east-1, us-west-2, eu-west-2, ap-southeast-2)Upstream (us-east-1, us-west-2, eu-west-2, ap-southeast-2)

Update timeline

investigating Apr 15, 2026, 05:59 PM UTC

We are currently investigating reports of resolution issues affecting some users who have updated to our latest version or are deploying the new version of our DNS Client, specifically when attempting to access certain sites that were previously blocked. Our team is actively working on a solution to ensure uninterrupted access for all users
resolved Apr 20, 2026, 08:23 AM UTC

We identified an issue affecting some users running the latest version of our DNS Client when accessing certain sites that were previously blocked. This behavior was linked to recent changes in upstream load balancing behavior during the handling of HTTP/2 to HTTP/1.1 traffic, including differences in how headers and compression are processed and forwarded between services. The agent now operates with both formats and compression strategies in our load balancer and edge environments. With this update, resolution behavior has been restored and access should now be functioning as expected.