Between 20:46 and 20:52 UTC on May 20, 2026, our uptime monitor recorded HTTP 403 Forbidden responses for https://resumiq.ru/ from probes in three regions (Europe, North America, Australia). The service recovered automatically without any intervention from our side. The most likely cause is a bot-protection or rate-limiting rule on our CDN edge that briefly flagged BetterStack's monitoring requests.
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 User-Agent as automated traffic and temporarily blocked it. The fact that the block lifted on its own across all regions within 3–6 minutes is consistent with a rate-limit window expiring rather than a permanent rule.
We have not yet definitively confirmed the rule that produced the 403 — that requires inspecting CDN access logs around the affected timestamps.
Resolution
The incident self-resolved as the suspected rate-limit window expired across all three monitoring regions. No deploys, configuration changes, or manual interventions were made during the incident.
Affected services
resumiq.ru