what happened
Bolt.new had a bigger problem on June 8, 2026, starting around 10:10 UTC. It lasted about three hours and twenty minutes, recovering at 13:32 UTC. Bolt.new has since reported the issue resolved. No further detail about the cause is available from the official source.
who this hits and how they usually find out
If you build something on Bolt.new, an outage like this does not announce itself to you. There is no email, no pop-up, no alert. You find out when a customer writes in asking why something is broken, or when you happen to open the tool yourself and notice things are not moving. That gap, between when the trouble starts and when you hear about it, is often measured in hours. For a solo operator or a small team, that is a long time to be in the dark while customers are already frustrated.
why this is especially rough without a technical background
When a tool like this goes quiet, there is nothing to look at. No log file, no error message on your screen, no red light anywhere in your workspace. The work just stops. Automations that should have run do not run. Apps that should have responded go silent. The first real signal is often a customer asking what is wrong, at which point you are already behind. You have to explain a problem you did not know existed, caused by a service you do not control, using information you do not have. That is a hard position to be in.
timeline
- 10:10 UTC, June 8, 2026 – Bolt.new begins experiencing a bigger problem.
- About 3 hours and 20 minutes – the disruption continues with no recovery.
- 13:32 UTC, June 8, 2026 – Bolt.new recovers and later reports the issue resolved.
How a watcher catches this before your users do
NoCrash reads Bolt.new’s public status page every minute. The moment that page flips from working to having trouble, NoCrash sends you a plain-language message explaining what is wrong, in words you can act on, without needing to interpret anything technical. On June 8, that would have meant a heads-up within a minute of Bolt.new’s own public report, well before most customers had a chance to notice and write in.
Beyond watching the tool itself, NoCrash also watches the things you ship. If you have n8n workflows, it watches those through your API token. If you have an app, it watches it through a URL you give it or a small JS snippet you add. So if something goes quiet on your own side, separate from what Bolt.new reports, that surfaces too.
None of this is magic. NoCrash does not know about trouble before Bolt.new’s own status page says so. But it means you are reading that status page every minute without having to remember to check, and the news arrives in plain English, in one place, next to everything else you build on. The difference between “my customer told me” and “I got a calm heads-up first” is usually just whether someone was watching.
the authoritative account
For the official record of this outage, see the Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.