OpenAI straight up DoSed a site I manage for my in-laws a few months ago.
AI crawlers, fetchers are blowing up websites; Meta, OpenAI are worst offenders
21–30 of 148 posts
Re: AI crawlers, fetchers are blowing up websites; Meta, OpenAI are worst offenders
#22OpenAI straight up DoSed a site I manage for my in-laws a few months ago.
What is it about? I'm curious what kinds of things people ask that floods sites.
Re: AI crawlers, fetchers are blowing up websites; Meta, OpenAI are worst offenders
#23Earlier quoted context omitted.
Much of it is not training. The LLMs fetch webpages for answering current questions, summarize or translate a page at the user's request etc. Any bot that answers daily political questions like Grok has many web accesses per prompt.
While it’s true that chatbots fetch information from websites in response to requests, the load from those requests is tiny compared to the volume of requests indexing content to build training corpuses. The reason is that user requests are similar to other web traffic because they reflect user interest. So those requests will mostly hit content that is already popular, and therefore well-cached. Corpus-building craw…
Re: AI crawlers, fetchers are blowing up websites; Meta, OpenAI are worst offenders
#24They mention anubis, cloudflare, robots.txt – does anyone have experiences with how much any of them help?
To stop malicious bots like this, Cloudflare is a great solution if you don't mind using it (you can enable a basic browser check for all users and all pages, or write custom rules to only serve a check to certain users or on certain pages). If you're not a fan of Cloudflare, Anubis works well enough for now if you don't mind the branding.
Here's the cloudflare rule I currently use (vast majority of bot traffic originates from these countries):
ip.src.continent in {"AF" "SA"} or
ip.src.country in {"CN" "HK" "SG"} or
ip.src.country in {"AE" "AO" "AR" "AZ" "BD" "BR" "CL" "CO" "DZ" "EC" "EG" "ET" "ID" "IL" "IN" "IQ" "JM" "JO" "KE" "KZ" "LB" "MA" "MX" "NP" "OM" "PE" "PK" "PS" "PY" "SA" "TN" "TR" "TT" "UA" "UY" "UZ" "VE" "VN" "ZA"} or
ip.src.asnum in {28573 45899 55836}Re: AI crawlers, fetchers are blowing up websites; Meta, OpenAI are worst offenders
#25They mention anubis, cloudflare, robots.txt – does anyone have experiences with how much any of them help?
Re: AI crawlers, fetchers are blowing up websites; Meta, OpenAI are worst offenders
#26I just set a rate-limit in cloudflare because no legitimate symbol server user will ever be excessive.
Re: AI crawlers, fetchers are blowing up websites; Meta, OpenAI are worst offenders
#27In the same time it’s so practical to ask a question and it opens 25 pages to search and summarize the answer. Before that’s more or less what I was trying to do by hand. Maybe not 25 websites because of crap SEO the top 10 contains BS content so I curated the list but the idea is the same no ?
My personal experience is that OpenAI's crawler was hitting a very, very low traffic website I manage 10s of 1000s of times a minute non-stop. I had to block it from Cloudflare.
Re: AI crawlers, fetchers are blowing up websites; Meta, OpenAI are worst offenders
#28Is the reason these large companies don't care because they are large enough to hide behind a bunch of lawyers?
Re: AI crawlers, fetchers are blowing up websites; Meta, OpenAI are worst offenders
#29Earlier quoted context omitted.
My personal experience is that OpenAI's crawler was hitting a very, very low traffic website I manage 10s of 1000s of times a minute non-stop. I had to block it from Cloudflare.
Where is caching breaking so badly that this is happening? Are OpenAI failing to use etags or honour cache validity?
Re: AI crawlers, fetchers are blowing up websites; Meta, OpenAI are worst offenders
#30Earlier quoted context omitted.
Much of it is not training. The LLMs fetch webpages for answering current questions, summarize or translate a page at the user's request etc. Any bot that answers daily political questions like Grok has many web accesses per prompt.
While it’s true that chatbots fetch information from websites in response to requests, the load from those requests is tiny compared to the volume of requests indexing content to build training corpuses. The reason is that user requests are similar to other web traffic because they reflect user interest. So those requests will mostly hit content that is already popular, and therefore well-cached. Corpus-building craw…