On the morning of July 21, 2026, Bolt.new reported a bigger problem starting at 07:20 UTC. The disruption lasted about an hour and was marked resolved at 08:55 UTC. Bolt.new has since confirmed the issue is cleared.
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 are not. So when something goes wrong, the first signal is usually a customer writing in to say something is broken, or a collaborator asking why a project will not load. By then the outage may already be half over, but you have spent that time confused, not informed. The gap between “it stopped working” and “I found out” is where the damage happens.
Why it is especially rough without a technical background
When a tool like Bolt.new has trouble, there is no error message sent to you. Nothing in your inbox. The work just stops moving. If you are not an engineer, you have no logs to check and no place to look. You might spend twenty minutes wondering if you did something wrong before it even occurs to you that the tool itself is the problem. Then you have to go find the status page, figure out what the jargon means, and decide whether to wait or start telling people. That whole process takes time you do not have, and it starts with a customer already unhappy.
What the timeline looked like
- 07:20 UTC – Bolt.new reported a bigger problem beginning
- About 1 hour – the disruption lasted
- 08:55 UTC – Bolt.new marked 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, in words you can act on, without you having to go find it yourself. That is the difference between “my customer told me at 08:40” and “I got a calm heads-up at 07:21.”
It also watches the things you ship. If you have n8n workflows, NoCrash watches those through your API token. If you have an app, it watches that through a URL you give it or a small JS snippet you drop in. So if your own side goes quiet separately, that surfaces too, in the same place.
What it does not do: it does not find trouble before Bolt.new’s own status page does. It reads that page and tells you quickly. That is the honest version of what it is.
For the authoritative account of this outage, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.