FIREHOL3 blacklisted bitbucket.org (104.192.141.1)

[Metsvahi]

Hi,

it seems bitbucket.org (104.192.141.1) has gotten into FIREHOL3 blacklist and so the requests are blocked for our servers to access git.

ping bitbucket.org
PING bitbucket.org (104.192.141.1) 56(84) bytes of data.
--- bitbucket.org ping statistics ---
197 packets transmitted, 0 received, 100% packet loss, time 195955ms

https://iplists.firehol.org/?ipset=firehol_level3

https://check.spamhaus.org/listed/?searchterm=104.192.141.1

Hopefully get it fixed soon and the server can access bitbucket again.

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

You will need to talk to the administrators of your firehol service.  There's nothing we can do here.

[Metsvahi]

Are there any alternative IP aadresses i can use somehow to bypass the block?

My server hoster said i need to contact bitbucket for them to fix the problem..

From SpamHaus page, it sais that the IP can only get delisted from the blacklist if Bitbucket.org contacts its ISP and asks them to contact SpamHaus, not any other way or am i mistaken?

[Nic Brough -Adaptavist-]

No, there are no proxies.  

Atlassian are not responsible for external blocking, it's not up to them to maintain other systems.

You need to get your server hosts to get Spamhaus to remove their incorrect block.

Give them https://support.atlassian.com/organization-administration/docs/ip-addresses-and-domains-for-atlassian-cloud-products/https://support.atlassian.com/organization-administration/docs/ip-addresses-and-domains-for-atlassian-cloud-products/ as the list of IP ranges they should not be blocking.