Hi there,
I noticed that our Amplitude events were showing a large number of events, particularly in December, from an apparent search bot. Reverse-lookup of the IP pointed to PetalBot from petalsearch.com at IP range 114.119.***
Has anyone else seen this or figured out how to fix? I’m wondering if this is something that should be filtered out at the Amplitude library level or has been fixed in a future version already.
Thanks!
+10Hey
I’m not aware of any configuration settings on the Amplitude SDK level which help block a certain IP.
The most common solution for this would be to implement a block filter in the Data/Govern part using the specific IP address.
This works well if the number of IP addresses to be blocked is at a manageable level.
If you are sending data via HTTP API, then maybe a middle layer can filter out the IP captured and not forward events to Amplitude . This can help manage the blocking part on your end itself.
Hope this helps.
I’m curious if Amplitude would look into this on their end too - presumably, they are already filtering out known web crawlers and bots at some level and would just need to add this to their list of ones to check for.
+10If you don't have an Amplitude account, you can create an Amplitude Starter account for free and enjoy direct access to the Community via SSO. Create an Amplitude account. You can also create a Guest account below!
If you don't have an Amplitude account, you can create an Amplitude Starter account for free and enjoy direct access to the Community via SSO. Create an Amplitude account. Want to sign up as a guest? Create a Community account.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
