Why you block Google ASN15169?

[shinebay]

This will block Googlebot to visit your site

[iwv]

If you run your website using cloudflare, you can use "known bots" feature

[zefir-git]

This will block Googlebot to visit your site

Then don't use the list to block access to your website. Perhaps just prevent flagged users from registering/logging in.

[zakigatez]

shinebay

which one is the one that blocks google crawlers, I had a problem with the google search console.

[khanakia]

I had the same issue it blocked the Google bot. Then I checked one of ASN15169 we used from this list caused the issue.

[ingereck]

Same here, blocking AS15169 results in a "Not eligible
Disapproved (Destination not working)" error in Google Ads. Can be tested in Google Search Console. I removed the ASN from my list

[zefir-git]

Just quoting the first line of the README:

An open-source list of ASNs known to belong to cloud, managed hosting, and colocation facilities.

Given that Google is a cloud provider, its ASN seems to belong in the list by definition.

This repo provides a list—not an implementation. How you choose to apply it is entirely up to you.

That said, from your mention of Googlebot and Google Ads, it sounds like you’re blindly dropping every request from ASNs on this list, presumably on a website.

Why would you block access to your entire site? Does it really hurt your app to serve public pages to requests coming from cloud providers?

If there’s a specific place where it actually matters that requests come from residential ISPs, e.g. authenticated or usage-sensitive parts of your service, then maybe try applying filtering only there, instead of dropping connections globally.