Why artifacts.elastic.co/GPG-KEY-elasticsearch returns 403 for russian IPs, but not always?

Elastic In Your Native Tongue Вопросы на русском языке
25

@Hugo_Blom @tibyke this has been resolved, apologies for the delay.

26

thx @warkolm
I can confirm that it's already http 200

27

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

28

@warkolm hi
can you please unblock NL?

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

29

Hey there.
Singapore also banned 151.192.123.178
ISP: Singtel

30

Hello, I can confirm that the old IP range was fixed :slight_smile:

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!

33

How possible is it that you have users from Russia accessing services via that range?