Cloudflare has new interesting analytics and capabilities. For instance, you can see (and even block) how many hits your website gets from specific crawlers, including AI scrapers. These are the last 24 hours stats for my website:
OpenAI hit my website 489 times in the last 24 hours alone, versus 87 for Googlebot. What the heck are they doing there, it`s not as if my website is a 100+ pages site...
Another interesting metric: fwupdate.asuswrt-merlin.net was resolved over 641K times in the last 24 hours. This does not directly translate to the number of installed routers since AMTM will also generate its own hits on that hostname, but it`s still a lot more than I expected. Unfortunately, Cloudflare's free plan does not expose more granular stats, such as how many hit I actually get daily on the firmware update manifest file. Back in the day when I only had the update checker behind Cloudflare, I was getting around 250K hit per day, which indicated roughly a similar number of routers running Asuswrt-Merlin.
I love stats. Sadly, I doubt that implementing an Opt-In method for me to determine the size of the installed userbase would be useful, as opt-in would probably only cover a small fraction of the installed userbase.
OpenAI hit my website 489 times in the last 24 hours alone, versus 87 for Googlebot. What the heck are they doing there, it`s not as if my website is a 100+ pages site...
Another interesting metric: fwupdate.asuswrt-merlin.net was resolved over 641K times in the last 24 hours. This does not directly translate to the number of installed routers since AMTM will also generate its own hits on that hostname, but it`s still a lot more than I expected. Unfortunately, Cloudflare's free plan does not expose more granular stats, such as how many hit I actually get daily on the firmware update manifest file. Back in the day when I only had the update checker behind Cloudflare, I was getting around 250K hit per day, which indicated roughly a similar number of routers running Asuswrt-Merlin.
I love stats. Sadly, I doubt that implementing an Opt-In method for me to determine the size of the installed userbase would be useful, as opt-in would probably only cover a small fraction of the installed userbase.