The public bucket URL is quick to use, but it is failing at the customer’s busiest media moment.
Friday’s campaign needs dependable media delivery while the customer needs a path that does not require a mobile release.
Who you’d be doing this for
“Our preview worked in testing, then the content team started asking why half the clips won’t load.”
Cansu Rahmani · Mobile Engineering Lead
Leads the application team whose campaign preview retrieves media from R2.
What is at stake
Campaign-preview users are seeing media failures through the public bucket URL. You must weigh a fast cutover against enough validation to protect the campaign.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- campaign speed vs. production validation
- public media access vs. request control
- immediate mitigation vs. durable platform adoption
- customer confidence vs. change risk
Why Cloudflare
R2 Object Storage becomes a durable production layer when it is connected to the developer platform rather than exposed as a standalone public bucket.
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.