it appears my json files are being marked as dynamic aswell

and not being cached

You need to enable Cache Everything for that

ah i see

i'll look at turning that on

most of my files are cacheable so r2's response times aren't the hugest of deal

as i know cloudflares cdn will give good responses

but was just surprised to see it

hey, is anyone experiencing slow r2 downloads in us region?

fyi, something's definitely up atm. game server boots usually take 30s, taking about 15-20m right now

How fast are assets marked with the path

/tile/*

for you on this page: https://maps.goalastair.com ?

im in london atm, but the issue my prod cluster is experiencing is in NA

Hm yeah, that does look a fair bit slower than it should be

is there a way we can get the word to someone or do i need to submit an email or something

It has been raised internally

epic tyvm

Hello here, I am migrating a project using the JS aws-sdk v2 to the v3 because the v2 will be not maintained in the future. I have an issue with the CompleteMultipartUploadCommand, I use the exact same params as I used in the V2 but I got an error. "The XML you provided was not well formed or did not validate against our published schema." After some tests, I discovered the Etag don't have quotes at the begining and the end of the value (but have it with the v2 official sdk) It's exactly the same bug described here but I think it's not fixed yet : https://community.cloudflare.com/t/r2-multipart-upload-not-working-with-minio-client-mc/396373 Any information about that?

is r2 locally/globally redundant?

(super common question I'm sure)

It is replicated within a region(for redundancy), but not globally

Hi, I will DM you to follow up on this.

I'm seeing intermittent errors with R2.put currently:

Error: put: We encountered an internal error. Please try again. (10001)

Is there any way to get more detailed information?

Hi everyone. I've tried to use S3 layer of the R2, but apparently multi part upload does fully work, in my testing it works only for two parts, not more, and for 3 parts I have an error:

xml
<?xml version="1.0" encoding="UTF-8"?><Error><Code>InvalidPart</Code><Message>There was a problem with the multipart upload.</Message></Error>

I've managed to find only one issue, that could be related, that was with double quotes for

ETag

(https://community.cloudflare.com/t/r2-multipart-upload-not-working-with-minio-client-mc/396373), but I have all

ETag

in double quotes, and the error is different.

Are your 1st and 2nd parts the exact same size?

@kian no, different

multipart uploads each part has to be the same size except for the last

Any insights about is this a subject to change in R2 storage, or not?

No that same limitation is in the S3 api and thus also in R2

Actually there are no such limitations on S3/GCS, that's why I was asking

BTW any links to the doc for R2 that has this limitation enumerated? The only bit that I was able to find was changelog entry - https://developers.cloudflare.com/r2/reference/changelog/ > Multipart upload part sizes are always expected to be of the same size, but this enforcement is now done when you complete an upload instead of being done very time you upload a part.