Exactly when I migrated to the website translator (February 18th) from js-proxy-translator our CDN usage tripled. This has caused us to exceed the free limit for the first time ever.
This certainly feels like a bug with the new website translator, as there’s no way that just migrating to a new tool, would increase the traffic on our website.
There also seems to be a mismatch in the the reported requests. One says over 1M requests, while the others sum to under 700k.
Lastly, how is there no way to disable requests that would cause charges? Our project is free and open source, and we do not have the funding to pay for traffic usage (especially when it’s seemingly inaccurate usage).
We’re going to review this internally to better understand the increase in CDN requests after the migration to Website Translator and the difference between the totals shown in the usage section and the project statistics. I’ve shared the details with our team so they can take a closer look.
We’ll get back to you as soon as we have more information
If you’re wondering why the usage has decreased since I reported this, it’s because I put a workaround in place to avoid using Crowdin’s CDN on my sites. Even without using the CDN myself, the usage is still half of what it was before I migrated to the website translator.
There is still some usage being observed though. I have no idea where this usage is coming from. My only assumption is that some AI company is scraping the crowdin distributions, which is incredibly easy to do since they are not protected by authentication. Could it be possible to lock down the CDN via a token or other type of authentication?
Thank you for providing that additional context and the screenshot. Regarding your concern about scraping, please be assured that AI bots cannot scrape these distributions.
However, your report has been very helpful, and we have created a task to investigate exactly what is causing this residual traffic. You can refer to case number 64625 if you have any follow-up questions in the meantime.
We will be sure to update you as soon as we receive more detailed information from our engineering team.
