Skip to main content
Bolt.new

Custom Domain status reporting is degraded

Degraded Lasted 2h 47m · started · Bolt.new's page

Level
confirmed
Worst impact
Degraded
Down Index
20of 100

What to do

  • Check whether your product depends on Bolt.new. 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 2h 47m it lasted.

    Anything that failed between 2026-11-06 15:26 UTC and 2026-11-06 18:13 UTC may need a replay.
  • Subscribe to Bolt.new's feed to hear about the next one first. RSS feed

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

Updates from Bolt.new 3

  1. investigating

    We're currently investigating an issue.

    provider

  2. investigating

    We’re currently investigating an issue with Bolt’s ability to report the status of custom domains.

    provider

  3. resolved

    This issue 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-c7b83005e7

Is Bolt.new still down?

No, this incident was resolved 2026-11-06 18:13 UTC. For Bolt.new's live state, see https://down.guide/providers/bolt.

How long did it last?

2h 47m, from 2026-11-06 15:26 UTC to 2026-11-06 18:13 UTC, by the times Bolt.new posted.

What caused it?

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

Where does this come from?

Bolt.new's official status page, https://status.bolt.new, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.