Incidents reported on status page for Résumiq https://status.resumiq.ru/ https://d1lppblt9t2x15.cloudfront.net/logos/733894ab5ae800ea5a17d971b7eb1a89.png https://status.resumiq.ru/ en https://status.resumiq.ru/incident/1026740 Sat, 29 Aug 2026 01:20:15 -0000 https://status.resumiq.ru/incident/1026740#1a5c50115f1e8f668207afd49f82465f642f9c2f131d314319095b0a3436d94c In-depth description of what's going on. You can use markdown here https://status.resumiq.ru/incident/1013345 Sat, 22 Aug 2026 01:20:15 -0000 https://status.resumiq.ru/incident/1013345#273de06a4e31235c5aa95435d111fd3df700f29b7263f4019fe4c93027fce877 In-depth description of what's going on. You can use markdown here https://status.resumiq.ru/incident/1005179 Sat, 15 Aug 2026 01:20:15 -0000 https://status.resumiq.ru/incident/1005179#625f312f35dffe1c6f283f94a24eb565d8bf9bbc42d9ca7e1c3f3e084ee629eb In-depth description of what's going on. You can use markdown here https://status.resumiq.ru/incident/989715 Sat, 08 Aug 2026 01:20:15 -0000 https://status.resumiq.ru/incident/989715#f63e2d4ce1b254af19aedf591443e6a207a98cb40c63f7a07e08f1934fe850f1 In-depth description of what's going on. You can use markdown here https://status.resumiq.ru/incident/977398 Sat, 01 Aug 2026 01:20:15 -0000 https://status.resumiq.ru/incident/977398#037d5e56cf779d5c76c5dd69d112277b84a4bd415e283c3913263c8945dbb40a In-depth description of what's going on. You can use markdown here https://status.resumiq.ru/incident/967755 Sat, 25 Jul 2026 01:20:15 -0000 https://status.resumiq.ru/incident/967755#a4503412550d8cec18109589a47bab24d48295c6991c5cb060d2d11e6a6f419c In-depth description of what's going on. You can use markdown here https://status.resumiq.ru/incident/954535 Sat, 18 Jul 2026 01:20:15 -0000 https://status.resumiq.ru/incident/954535#f3d98381f1935da2fcc78d24fbf4ed9f228eed1b47d16356688a1d0551e1f0fc In-depth description of what's going on. You can use markdown here https://status.resumiq.ru/incident/943067 Sat, 11 Jul 2026 01:20:15 -0000 https://status.resumiq.ru/incident/943067#f3094a906df1893324aed570dc89d987378453118d616c29eff4f8cdee663634 In-depth description of what's going on. You can use markdown here https://status.resumiq.ru/incident/936638 Sat, 04 Jul 2026 01:20:15 -0000 https://status.resumiq.ru/incident/936638#9aaf13cc4136fb9323e7854845b4b157767d1626e1ebd1673806ba78fb775ab0 In-depth description of what's going on. You can use markdown here https://status.resumiq.ru/incident/929262 Sat, 27 Jun 2026 01:20:15 -0000 https://status.resumiq.ru/incident/929262#36502737633b2b8c0f018d5b1461e4e05c7278922d83b3366405763f2e792292 In-depth description of what's going on. You can use markdown here https://status.resumiq.ru/incident/922565 Sat, 20 Jun 2026 01:20:15 -0000 https://status.resumiq.ru/incident/922565#653e5837736b787d222a657be8373147b5da9ef3be1e82a60fd4d92e8bd78582 In-depth description of what's going on. You can use markdown here https://status.resumiq.ru/incident/915288 Sat, 13 Jun 2026 01:20:15 -0000 https://status.resumiq.ru/incident/915288#fd04c950a2b23f40472a2fb1dd7be495df3e9e1a3a8e6da48f93b69af1754277 In-depth description of what's going on. You can use markdown here https://status.resumiq.ru/incident/908555 Sat, 06 Jun 2026 01:20:15 -0000 https://status.resumiq.ru/incident/908555#f22715d352c3b7088e2f29b80f41333c684044d9d7f43720a5129e7759016930 In-depth description of what's going on. You can use markdown here https://status.resumiq.ru/incident/903321 Sat, 30 May 2026 01:20:15 -0000 https://status.resumiq.ru/incident/903321#b68e2f890e7725d1dc2632e16b082adb30979b0873ca8c597b88348b5d7fc7da In-depth description of what's going on. You can use markdown here https://status.resumiq.ru/incident/897001 Sat, 23 May 2026 03:20:15 -0000 https://status.resumiq.ru/incident/897001#97a3a4230a72fa6273f744708ddcabfcd7a7896d385d525fb64932513b041b54 Maintenance completed 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 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.