On September 2, 2026, Bolt.new had a significant disruption starting at 13:53 UTC. It lasted about two hours and was resolved by 16:33 UTC. Bolt.new has since confirmed the issue is resolved. No detailed cause has been published.
Who this kind of outage hits
If you build on Bolt.new, you probably found out about this the hard way. A customer tried something, it did not work, and they messaged you. Or you checked in hours later and noticed things had stalled. That is the normal shape of this kind of thing. The tool does not tap you on the shoulder. It just stops, quietly, and the first signal is usually someone unhappy on the other end.
That gap, between when the tool stops and when you find out, is where the damage happens. A support ticket arrives. A client loses confidence. A deadline slips. None of it was your fault, but you are the one explaining it.
Why it is especially rough without a technical background
If you are not an engineer, there is nothing to look at when something like this happens. No log file, no error on your screen, no alert. The work just stops moving. You might spend time wondering if you did something wrong, retracing your steps, before realizing the tool itself was the problem. By then, the disruption has already cost you time and possibly a customer relationship.
What the timeline looked like
- 13:53 UTC - Bolt.new started having a bigger problem
- ~15:53 UTC - roughly two hours in, the disruption was still active
- 16:33 UTC - Bolt.new recovered and confirmed the issue resolved
Total duration: about two hours and forty minutes.
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. Not a status code, not a raw alert. Something you can actually read and act on, in the same place where you watch 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 it watches that too. So if something goes quiet on your own side, that surfaces as well.
The honest limit: NoCrash reads the tool’s own public status page. It does not find the outage before Bolt.new reports it. What it does is catch the report within a minute and tell you in plain English, so you are not the last to know.
The difference is not magic. It is just that you hear it first, before a customer does, and you have a moment to get ahead of it.
For the authoritative account of this outage, see Bolt.new’s official status page at https://status.bolt.new/proxy/status.bolt.new.