Skip to main content
Cloudflare Workers

Errors adding R2 custom domains

Degraded Lasted 1h 53m · started · Cloudflare Workers's page

Level
confirmed
Worst impact
Degraded
Components
R2
Down Index
34of 100

What to do

  • Check whether you use Cloudflare Workers R2. 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 1h 53m it lasted.

    Anything that failed between 2026-05-05 11:33 UTC and 2026-05-05 13:26 UTC may need a replay.
  • Subscribe to Cloudflare Workers's feed to hear about the next one first. RSS feed

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

Updates from Cloudflare Workers 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-c149facd04

Is Cloudflare Workers still down?

No, this incident was resolved 2026-05-05 13:26 UTC. For Cloudflare Workers's live state, see https://down.guide/cloudflare-workers.

How long did it last?

1h 53m, from 2026-05-05 11:33 UTC to 2026-05-05 13:26 UTC, by the times Cloudflare Workers posted.

What was affected?

Cloudflare Workers named R2.

What caused it?

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

Where does this come from?

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