On July 7, 2026, Bolt.new had a significant disruption starting at 14:21 UTC. It lasted roughly one hour and was resolved by 16:03 UTC. Bolt.new has since confirmed the issue is resolved. The cause has not been published in detail.
Who this kind of outage hits
If you build or run something on Bolt.new, you probably did not have an alert waiting for you when this started. Most people find out the same way: a customer writes in, a collaborator asks why something is broken, or you happen to open the tool yourself and notice nothing is loading. By then, the disruption has already been running for a while. The gap between “it broke” and “I knew it broke” is where the damage happens, quietly.
Why it is especially rough without a technical background
When a tool like Bolt.new has a bigger problem, there is no error log to open, no red line on a graph to point at. The work just stops. A project that should have built does not build. A workflow that should have run sits there. Nothing tells you why. The first real signal is often an unhappy customer or a missed deadline, and by then you are already behind. You are not debugging the tool, you are managing the fallout.
What the timeline looked like
- 14:21 UTC - Bolt.new starts having a bigger problem.
- Roughly one hour - the disruption runs.
- 16:03 UTC - Bolt.new reports the issue resolved.
That is about 102 minutes from start to recovery, with no detailed cause published at the time of writing.
How a watcher catches this before your users do
NoCrash reads Bolt.new’s own public status page once every minute. The moment that page flips from working to having trouble, NoCrash sends you a plain-language message, in words you can act on, without you having to go check anything yourself. It does not find the problem before Bolt.new reports it, but it catches the report within a minute and tells you in plain English, sitting next to everything else you build on.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those through your API token. If you have an app, you can give it a URL or drop in a small JS snippet, and NoCrash watches that too. So a quiet stall on your own side surfaces the same way, in the same place. The result is that “my customer told me” becomes “I got a calm heads-up first, and I had a few minutes to say something before anyone asked.”
For the authoritative account of this outage, see the official Bolt.new status page: https://status.bolt.new/proxy/status.bolt.new