Previous incidents

May 20, 2026

Between 20:46 and 20:52 UTC on May 20, 2026, our uptime monitor recorded HTTP...

Resolved May 20, 2026 at 8:59pm UTC

Root cause (suspected)

All three probes received HTTP 403 simultaneously across three continents. This rules out a geographic block or a regional network issue. The request reached the edge (0.75 s response time) and was answered with a forbidden status, which points to a deliberate access policy rather than infrastructure failure.

The most likely cause is bot detection or rate-limiting at our CDN layer (Yandex Cloud CDN) that identified BetterStack's Better Stack Better Uptime Bot Use...

Previous updates