@WalshyMVP The problem was that even r2.cloudflarestorage.comwas blocked, not just r2.dev. The former domain is used for production.
For now and for me, it’s not blocked anymore, so I guess it’s now “fixed”?
With the link @/WalshyMVP also sent, what it literally meant was that you shouldn’t be using either of them (e.g. any of the “public & shared domains”), but connect your own domain.
In other words, if you have the domain example.com, connect something like e.g. r2.example.com, storage.example.com, or files.example.com to your R2 bucket.
Yep, for serving the files. But aren’t you supposed to use r2.cloudflarestorage.com when uploading the file?
If you want to pursue it any further, you would need to contact the customer support of these ISP’s, and complain to them.
I made formal complaint to local authority who are in charge of censorship. I’m waiting for the answer from them.
I searched further and yes, the official docs https://developers.cloudflare.com/r2/api/s3/api/ points you to use r2.cloudflarestorage.com for any S3 API interactions. (I can’t edit so I’m replying instead)