Regression on datacenter traffic filter? #6210
-
|
Hi, since a couple of weeks I get plenty of fake traffic reported in Plausible. My website's visitors are mainly from European country, and and use the site during daytime in Europe. Since 19th of March, I get plenty of visits from Mexico, China, Singapore, the US, at any time of the day and night. Checking my nginx logs, I was able to confirm that these visits are all from datacenter IP addresses (Tencent, Huawei). There are so many different IP addresses it's not really conceivable to block them all. Coincidentally, I upgraded plausible from 3.0.1 to 3.2.0 on the 14th of March - 5 days before the problem appeared. So I'm wondering: did I possibly mess something something during the upgrade? Or did Plausible's datacenter traffic filtering stop working? Something else? Related discussion or another apparently hit by the same spam traffic problem recently: #6206 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Thanks for the report @mef. I just wanted to clarify that our advanced bot and datacenter traffic filtering is a cloud-only capability and has never been part of the self-hosted release. On plausible.io we actively monitor traffic, maintain blocklists and filter out bots and datacenter traffic on an ongoing basis. This isn't something we can do on self-hosted instances. You can learn more about this and other differences between the cloud and self-hosted here. The 3.2.0 upgrade didn't change anything related to this, so the timing is coincidental. |
Beta Was this translation helpful? Give feedback.
Thanks for the report @mef.
I just wanted to clarify that our advanced bot and datacenter traffic filtering is a cloud-only capability and has never been part of the self-hosted release. On plausible.io we actively monitor traffic, maintain blocklists and filter out bots and datacenter traffic on an ongoing basis. This isn't something we can do on self-hosted instances. You can learn more about this and other differences between the cloud and self-hosted here.
The 3.2.0 upgrade didn't change anything related to this, so the timing is coincidental.