On July 21, 2026, Bolt.new reported a bigger problem starting at 11:25 UTC. It lasted about 22 minutes and was resolved by 11:48 UTC. Bolt.new has since confirmed the disruption is over.
Who this kind of outage hits
If you build or ship something on Bolt.new, a 22-minute window where things stop working can be invisible to you until it is not. Most operators find out the same way: a customer messages them, confused or annoyed, asking why something is broken. By then the outage is already over, but the damage to trust is done. There is no alert, no email, nothing inside the tool that says “hey, this stopped working at 11:25.” You are just the last to know.
Why it is especially rough without a technical background
When a tool like Bolt.new has a bigger problem, there is nothing on your screen that explains it. No error message you can read, no log file to open. The work just stops moving. A form does not submit, a workflow does not run, a build does not finish. If you do not know to go check a status page, you might spend real time wondering if you broke something, retracing your steps, or worse, staying quiet while customers hit the same wall. The first signal is usually an unhappy person, not a calm heads-up.
What the timeline looked like
- 11:25 UTC - Bolt.new’s own status page reported a bigger problem.
- 11:48 UTC - Bolt.new reported the disruption resolved.
- Total duration - about 22 minutes.
Bolt.new has not published a detailed cause beyond confirming it is resolved. See the official source linked at the bottom for any updates.
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 check anything. On July 21, that would have meant a heads-up within a minute of Bolt.new’s own report at 11:25, rather than finding out from a customer sometime after 11:48.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those too. If you give it a URL or add a small JS snippet to your app, it watches that side as well. So a quiet stall on your own side surfaces alongside anything happening at the tool level, in one place, in plain English.
NoCrash does not find outages before the tool’s own status page does. It reads that page and tells you fast, in language that does not require a technical background to act on.
For the authoritative account of this outage, see Bolt.new’s official status page: https://status.bolt.new/proxy/status.bolt.new