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

Is this from all IPs in the range @tibyke? If not, please DM me the relevant one.

I only have one address in that range, and it has been blocked for a couple of months now. (obviously I haven't done anything bad at all)
btw it's 971 backwards.
how come you don't know what the rules are? you set them up don't you?

I do not, no.

I'll get it checked.

any update on this one? (still 403)

# curl -qso/dev/null https://artifacts.elastic.co/packages/8.x/yum/8.2.0/kibana-8.2.0-x86_64.rpm -w "%{http_code}\n"
403
# curl -qso/dev/null https://artifacts.elastic.co/packages/8.x/yum/8.2.0/kibana-8.2.0-x86_64.rpm -w "%{http_code}\n"
200

thx!

Hi everyone, we're really sorry you're experiencing these issues. This is a very difficult problem to resolve so I wanted to at least explain why it's happening.

Elastic must comply with US and other applicable laws and rules regulating international trade. As you likely have heard, numerous Russian entities and persons have been sanctioned by the US, EU and many other governments as a result of Russia’s invasion of Ukraine. In addition, extremely strict controls have been imposed on exports of technology, including Elastic products, to Russian users.

These sanctions and controls prohibit conducting any business with sanctioned companies and persons and bar Elastic from exporting its technology to Russia. The standard way to determine network access is with geoip lookups, and we rely on our network providers to do accurate geoip lookups. This service is hosted through GCP. Google is a US-based company, and therefore has to obey those laws. Note that even if Google did not already provide this protection, we're obligated by US law to do it anyway. However, that's not technically what's causing the errors here.

When you encounter an IP that's blocked, I'm afraid all you can do is report it to us and wait while we engage the support team on your behalf. We actually experience this issue inside Elastic with our own cross-provider traffic and must work around it too. Thank for your continued patience.

Finally, please know that while we stand with Ukraine, we at Elastic are heartbroken that the people of Russia are also suffering from the actions of the Russian government. Many of our own employees have been directly affected by this conflict and we join the world in hoping that it will end as soon as possible.

6 Likes

Hello, I have full understanding in that you guys follow the requirement however it would be nice to update your GEOIP database before enforcing this.

We still experience issues with on of our /22 that was moved to Sweden over 2 years ago.

Would it be possible for you guys to "fix/check" our IP range? 91.197.40.0/22

Thanks in advance and just let me know in case of any questions/problems

ubuntu@testvm1:~$ curl -I https://artifacts.elastic.co/packages/7.x/apt/pool/main/e/elasticsearch/elasticsearch-7.16.1-amd64.deb
HTTP/2 403
content-length: 134
content-type: text/html; charset=UTF-8
date: Fri, 10 Jun 2022 12:28:42 GMT
alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000

Welcome to our community! :smiley: We aren't all guys though.

As Drew mentioned above, we do rely on Google's lookups here. We will raise this range with them and get it corrected.

2 Likes

my 403 is back again! what's going on here guys (and girls) ?
IP is the same as above

I've chased it up.

1 Like

any update?

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

1 Like

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

1 Like

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

@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

Hey there.
Singapore also banned 151.192.123.178
ISP: Singtel

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!

2 posts were merged into an existing topic: Are you getting 403's when downloading? Please read here first

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

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.