Suddenly getting "503 Service Unavailable" from R2

I have been using R2 to serve our site’s static assets for some time but recently, I’m getting “503 Service Unavailable” for some of the requests. Maybe 1 out of 100. But these issues are causing my page to turn blank since the served JS files aren’t working.

Any idea what could be happening? How do I resolve this?

  1. Checked using custom domain to serve from R2
  2. Checked turning off all security to essential off to ensure it’s not blocking

Some headers

Could it be because R2 have rate limit for requests? But it’s strange to see this when they only state that rate limits are only implemented for R2’s dev urls, and they recommend us to use custom domain for serving, which I already did.

I’m experiencing the same issue.

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.