# Why artifacts.elastic.co/GPG-KEY-elasticsearch returns 403 for russian IPs, but not always? **URL:** \ **Category:** Вопросы на русском языке\ **Created:** [March 29, 2022, 1:41pm UTC](https://discuss.elastic.co/t/why-artifacts-elastic-co-gpg-key-elasticsearch-returns-403-for-russian-ips-but-not-always/300969 "2022-03-29T13:41:47Z")\ **Posts on this page:** 9\ **Page:** 2
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [June 21, 2022, 10:45pm UTC](https://discuss.elastic.co/t/why-artifacts-elastic-co-gpg-key-elasticsearch-returns-403-for-russian-ips-but-not-always/300969/25 "2022-06-21T22:45:05Z")
@Hugo_Blom @tibyke this has been resolved, apologies for the delay. ---
**Author:** ![tibyke](https://avatars.discourse-cdn.com/v4/letter/t/bbce88/32.png) [@tibyke](https://discuss.elastic.co/u/tibyke)\ **Post date:** [June 21, 2022, 10:58pm UTC](https://discuss.elastic.co/t/why-artifacts-elastic-co-gpg-key-elasticsearch-returns-403-for-russian-ips-but-not-always/300969/26 "2022-06-21T22:58:14Z")
thx @warkolm I can confirm that it's already http 200 ---
**Author:** ![Dexanir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dexanir/32/107587_2.png) [@Dexanir](https://discuss.elastic.co/u/Dexanir)\ **Post date:** [June 26, 2022, 11:26am UTC](https://discuss.elastic.co/t/why-artifacts-elastic-co-gpg-key-elasticsearch-returns-403-for-russian-ips-but-not-always/300969/27 "2022-06-26T11:26:45Z")
Hello. We've got same error on our hosted server in Netherlands: IP Address: 176.124.203.84 Hostname: 176.124.203.84 ISP: Hosting technology LTD ---
**Author:** ![zzz\_sergio](https://avatars.discourse-cdn.com/v4/letter/z/a87d85/32.png) [@zzz\_sergio](https://discuss.elastic.co/u/zzz_sergio)\ **Post date:** [June 27, 2022, 5:39pm UTC](https://discuss.elastic.co/t/why-artifacts-elastic-co-gpg-key-elasticsearch-returns-403-for-russian-ips-but-not-always/300969/28 "2022-06-27T17:39:19Z")
@warkolm hi can you please unblock NL? ```auto root@nl-vds-ey0sy:~# curl -qs ipinfo.io | jq '.' { "ip": "45.134.254.36", "city": "Amsterdam", "region": "North Holland", "country": "NL", "loc": "52.3740,4.8897", "org": "AS9002 RETN Limited", "postal": "1012", "timezone": "Europe/Amsterdam", "readme": "https://ipinfo.io/missingauth" } ``` thank you ---
**Author:** ![igroykt](https://avatars.discourse-cdn.com/v4/letter/i/6de8d8/32.png) [@igroykt](https://discuss.elastic.co/u/igroykt)\ **Post date:** [July 8, 2022, 7:22am UTC](https://discuss.elastic.co/t/why-artifacts-elastic-co-gpg-key-elasticsearch-returns-403-for-russian-ips-but-not-always/300969/29 "2022-07-08T07:22:33Z")
Hey there. Singapore also banned 151.192.123.178 ISP: Singtel ---
**Author:** ![Hugo\_Blom](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hugo_blom/32/106876_2.png) [@Hugo\_Blom](https://discuss.elastic.co/u/Hugo_Blom)\ **Post date:** [July 13, 2022, 2:10pm UTC](https://discuss.elastic.co/t/why-artifacts-elastic-co-gpg-key-elasticsearch-returns-403-for-russian-ips-but-not-always/300969/30 "2022-07-13T14:10:47Z")
Hello, I can confirm that the old IP range was fixed 🙂 Sadly we have gotten a new IP range that doesn't work: `217.61.244.0/24` It looks like some others also reported a few ranges in this thread, maybe we could get another unblock round? Thanks in advance! ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 17, 2022, 11:00pm UTC](https://discuss.elastic.co/t/why-artifacts-elastic-co-gpg-key-elasticsearch-returns-403-for-russian-ips-but-not-always/300969/31 "2022-07-17T23:00:03Z")
Split this topic on July 17, 2022, 11:00pm UTC 2 posts were merged into an existing topic: [Are you getting 403's when downloading? Please read here first](https://discuss.elastic.co/t/are-you-getting-403s-when-downloading-please-read-here-first/307340/9) ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 17, 2022, 10:57pm UTC](https://discuss.elastic.co/t/why-artifacts-elastic-co-gpg-key-elasticsearch-returns-403-for-russian-ips-but-not-always/300969/33 "2022-07-17T22:57:50Z")
How possible is it that you have users from Russia accessing services via that range? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 14, 2022, 11:00pm UTC](https://discuss.elastic.co/t/why-artifacts-elastic-co-gpg-key-elasticsearch-returns-403-for-russian-ips-but-not-always/300969/34 "2022-08-14T23:00:56Z")
Closed on August 14, 2022, 11:00pm UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed. [Previous page](https://discuss.elastic.co/t/why-artifacts-elastic-co-gpg-key-elasticsearch-returns-403-for-russian-ips-but-not-always/300969.md?page=1)