On July 10, 2026, Bolt.new reported a bigger problem starting at 14:40 UTC. It lasted about 23 minutes and was marked resolved at 15:03 UTC. Bolt.new’s own status page confirms the disruption is over.
Who this kind of outage hits
If you build on Bolt.new, you probably are not watching its status page while you work. Most people find out something broke because a customer writes in, or because they go to check on something and notice the work never finished. By then the disruption is already over, but the damage is done: a customer is annoyed, a deadline slipped, or a workflow that was supposed to run quietly just did not. The gap between “it broke” and “I found out” is almost always measured in hours, not minutes.
Why it is especially rough without a technical background
When a tool like this goes quiet, there is no error message waiting for you. Nothing flashes red. The work just stops moving. If you are not an engineer, you have no logs to dig through and no obvious place to look. The first real signal is often an unhappy customer asking why something did not happen. At that point you are already behind, explaining a problem you did not know existed until someone else told you about it.
What the timeline looked like
- 14:40 UTC - Bolt.new reported a bigger problem beginning.
- 15:03 UTC - Bolt.new marked the disruption resolved.
- Total duration - about 23 minutes.
The disruption was short. But 23 minutes is long enough for automated workflows to queue up silently, for a customer to notice something missing, or for a build to fail without any obvious reason surfacing on your end.
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, without you having to go looking. That turns “my customer told me two hours later” into “I got a heads-up within a minute of Bolt.new’s own report.”
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, without you having to check anything manually.
To be clear about what it does not do: NoCrash does not find the outage before Bolt.new’s own status page does. It reads that page and tells you fast, in plain English, alongside everything else you build on.
For the authoritative account of this disruption, see Bolt.new’s official status page at https://status.bolt.new/proxy/status.bolt.new.