Skip to main content
Cloudflare

Elevated number of R2 503 errors in Eastern North America region

Degraded Lasted 3h 32m · started · Cloudflare's page

Level
confirmed
Worst impact
Degraded
Components
R2
Regions
us

What to do

  • Check whether you use Cloudflare R2 in us. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 3h 32m it lasted.

    Anything that failed between 2026-09-04 21:10 UTC and 2026-09-05 00:42 UTC may need a replay.
  • Subscribe to Cloudflare's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=cloudflare works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Cloudflare 1

  1. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-aca995c573

Is Cloudflare still down?

No, this incident was resolved 2026-09-05 00:42 UTC. For Cloudflare's live state, see https://down.guide/cloudflare.

How long did it last?

3h 32m, from 2026-09-04 21:10 UTC to 2026-09-05 00:42 UTC, by the times Cloudflare posted.

What was affected?

Cloudflare named R2 in us.

What caused it?

Cloudflare hasn't published a root cause. If it does, it shows here.

Where does this come from?

Cloudflare's official status page, https://www.cloudflarestatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.