On the morning of July 23, 2026, Bolt.new reported a bigger problem starting at 08:01 UTC. The disruption lasted about an hour and was marked resolved at 09:36 UTC. Bolt.new has since confirmed the issue is cleared.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, your projects, your automations, your whole workflow sits on top of it. When it goes quiet, nothing inside the tool tells you. There is no alert, no red banner, no email. The first signal is usually a customer writing in to say something is broken, or a collaborator asking why nothing is loading. By that point, the outage may already be half over, but you have spent the whole time in the dark, maybe even apologizing for something you did not cause and could not have prevented.
Why this is especially rough if you are not an engineer
An engineer can pull logs, check error traces, and at least confirm the problem is upstream. A solo operator or a non-technical founder has none of that. The work just stops moving. A form stops submitting, a build stops generating, a workflow stops running, and there is no error on the screen to point at. You start second-guessing yourself. You wonder if you broke something. You spend time checking things that are fine, while the real problem sits on Bolt.new’s side and you have no way to know it.
Timeline
- 08:01 UTC - Bolt.new reports a bigger problem begins.
- 09:36 UTC - Bolt.new marks the issue resolved.
- Total duration - about 1 hour.
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, in words you can act on, sitting next to everything else you build on. You do not have to go check the status page yourself, and you do not have to wait for a customer to tell you.
That is the honest shape of what it does. NoCrash reads the tool’s own public report, so it catches the trouble within a minute of Bolt.new’s own announcement, not before it. It also watches the things you ship: your n8n workflows through an API token, and your app through a URL you give it or a small JS snippet you drop in. So if the problem is on your side rather than Bolt.new’s side, that surfaces too.
The difference between “my customer told me an hour in” and “I got a calm heads-up at 08:01” is not magic. It is just having something read the status page so you do not have to.
The authoritative account
For the official record of this outage, go to Bolt.new’s own status page: https://status.bolt.new/proxy/status.bolt.new