Deno Deploy: Registering new and renew existing custom domains

What to do

Check whether you use Deno Deploy Console. 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 0m it lasted.
Anything that failed between 2026-06-03 09:39 UTC and 2026-06-03 09:39 UTC may need a replay.
Subscribe to Deno Deploy's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=deno-deploy works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

resolvedJun 3, 2026, 9:39 AM UTC
Type: Incident Duration: 3 hours and 15 minutes Affected Components: Console Jun 3, 12:54:37 GMT+0 - Resolved - This incident has been resolved. Jun 3, 09:39:51 GMT+0 - Identified - Register new domains and renewing existing ones is failing on certificate validation. We are currently investigating this incident. It looks like other people using the same certificate provider are also having issues the same issues.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

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

Is Deno Deploy still down?

No, this incident was resolved 2026-06-03 09:39 UTC. For Deno Deploy's live state, see https://down.guide/deno-deploy.

How long did it last?

0m, from 2026-06-03 09:39 UTC to 2026-06-03 09:39 UTC, by the times Deno Deploy posted.

What was affected?

Deno Deploy named Console.

What caused it?

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

Where does this come from?

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