Skip to content

Conversation

@liviuconcioiu
Copy link
Collaborator

No description provided.

Copy link
Member

@sgiehl sgiehl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've looked through the list of new bots, but wasn't able to find further details for a couple of them. But as long as you have some evidence they appeared somewhere, I guess it should be fine to add them.

@liviuconcioiu
Copy link
Collaborator Author

I've looked through the list of new bots, but wasn't able to find further details for a couple of them. But as long as you have some evidence they appeared somewhere, I guess it should be fine to add them.

All bots in this PR were found in my logs. I also managed to find the Google-Firebase bot #8170 (comment) and another Google-ilp that come from IPs used by Google's crawlers:

Logs from April & May:

66.249.89.13,rate-limited-proxy-66-249-89-13.google.com,Google-Firebase
66.249.89.14,rate-limited-proxy-66-249-89-14.google.com,Google-Firebase
66.249.89.15,rate-limited-proxy-66-249-89-15.google.com,Google-Firebase

66.249.82.68,google-proxy-66-249-82-68.google.com,Google-ilp
64.233.173.4,google-proxy-64-233-173-4.google.com,Google-ilp
64.233.173.2,google-proxy-64-233-173-2.google.com,Google-ilp

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants