South Korean government blocked Cloudflare R2

Developers Storage
1 
$ nslookup -query=ns cloudflarestorage.com.
Server:    bns1.hananet.net
Address:  210.220.163.82

cloudflarestorage.com   nameserver = localhost

SK Broadband (South Korean ISP, AS9318) name servers (210.220.163.82, 219.250.36.130) are resolving NS records of cloudflarestorage.com to localhost.

Note Korean ISPs use DNS poisoning to block certain sites, so this may be in response to legal requests blocking its subdomain.

2

I suggest you to contact SK Broadband about that, as they are the only ones that will be able to remediate issues within their network.

After all, the blocking that you refer to, is happening within SK Broadband’s reach.

3

South Korean government blocked Cloudflare R2, including r2(.)dev and r2.cloudflarestorage(.)com

Web services that located in South Korea can’t connect to R2 API.

IMG_4185
IMG_41851170Ă—1067 107 KB

6

image
image735Ă—433 102 KB

7

image
image716Ă—158 38.8 KB

8

Someone else mentioned this before:

Not much Cloudflare can do when a Government decides to block something. Which ISP is it? Have you tried others?

1 Like
9

This is also why we say r2.dev is not for production use, please use a proper domain for R2.

1 Like
11

@WalshyMVP The problem was that even r2.cloudflarestorage.com was 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”?

1 Like
12

It blocked from all of Korea’s major ISPs (KT, SK, LG U+)

13

And in SK Broadband DNS does not resolve cloudflarestorage.com, where I responded:

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.

If you want to pursue it any further, you would need to contact the customer support of these ISP’s, and complain to them.

15

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.

16

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)