CDN reported down by a faulty check

resolved · began 30 Sep 2026 22:58 UTC · resolved 30 Sep 2026 23:08 UTC · lasted 10m

Timeline

resolved 30 Sep 2026 23:45 UTC

Resolved

investigating 30 Sep 2026 23:44 UTC

Investigating

What happened

Monitoring fault, not a CDN fault. A check deployed at 22:57 UTC required proof of an edge cache hit; Bunny Shield challenged our prober addresses, so that proof could not arrive and all four regions failed together. The CDN served normally throughout.