Multipart retries are being treated like new upload pressure.
The gateway must preserve bucket protection while allowing a valid upload to continue after a transient failure.
Who you’d be doing this for
“Our upload workers spent the afternoon retrying the same parts, and the queue just kept growing.”
Rafael Cruz · Backend Engineer
Maintains a media-processing service that sends large customer uploads to R2 through an S3-compatible SDK.
What is at stake
Avoidable 429 responses are forcing multipart upload clients to retry the same object parts. You must weigh smoother uploads against the bucket protection that keeps shared request capacity stable.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- upload completion vs bucket protection
- gateway simplicity vs storage-side work
- retry tolerance vs abuse resistance
- release speed vs request-path confidence
Why Cloudflare
R2’s S3-compatible request path is where application developers experience whether durable object uploads continue under load.
Written with these in mind
Not your kind of problem? 51 more at Cloudflare, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.