Incidents | Résumiq Incidents reported on status page for Résumiq https://status.resumiq.ru/ https://d1lppblt9t2x15.cloudfront.net/logos/733894ab5ae800ea5a17d971b7eb1a89.png Incidents | Résumiq https://status.resumiq.ru/ en Регулярная очистка и профилактика https://status.resumiq.ru/incident/897001 Sat, 23 May 2026 01:20:15 -0000 https://status.resumiq.ru/incident/897001#fdbbc01eeea54947c7a03670aaf08f60b28409c8322c9f9414a53cf5fb5163bc In-depth description of what's going on. You can use markdown here resumiq.ru/create recovered https://status.resumiq.ru/ Thu, 21 May 2026 07:49:39 +0000 https://status.resumiq.ru/#6dfa6610a92121a1ae7b2e72ac98564aea0c5fa91459aa197609e155af043ae3 resumiq.ru/create recovered resumiq.ru/create went down https://status.resumiq.ru/ Thu, 21 May 2026 07:39:57 +0000 https://status.resumiq.ru/#6dfa6610a92121a1ae7b2e72ac98564aea0c5fa91459aa197609e155af043ae3 resumiq.ru/create went down 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. https://status.resumiq.ru/incident/901103 Wed, 20 May 2026 20:59:00 -0000 https://status.resumiq.ru/incident/901103#85a69740430751c857c6bd16ce2d4e3b36a63810b31aa3f020f7f6cf6bb35ffa ## 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. resumiq.ru recovered https://status.resumiq.ru/ Wed, 20 May 2026 20:52:47 +0000 https://status.resumiq.ru/#b5e21cc66c458a616618b2ed707efca3b7df09ab911291e567eaafe1c9a909ca resumiq.ru recovered resumiq.ru went down https://status.resumiq.ru/ Wed, 20 May 2026 20:46:38 +0000 https://status.resumiq.ru/#b5e21cc66c458a616618b2ed707efca3b7df09ab911291e567eaafe1c9a909ca resumiq.ru went down