zlacker

Had similar issue in recent past, and was able to get it solved via the Discord channel. From what I understood is that it requires a manual over-ride on R2/ Workers because the thing that checks for the 2.8 TOS violation is not able to see the difference between Workers/ R2 and the standard CDN service.

If you go to the R2 Discord channel you see this happening every other week.

What is also kinda annoying is customers can't create support tickets because it requires a plan. Which imo is bad given these customers pay for R2 and often have a ton of data on it (which is why the 2.8 gets hit...).

Hopefully you can get this fixed permanently (for all customers at once, and not case-by-case).