On July 27, 2026, Bolt.new had a significant problem starting at 11:35 UTC. It lasted about two hours and was resolved by 13:35 UTC. Bolt.new has since reported the disruption as resolved. No detailed cause has been published.
Who this kind of outage hits
If you build on Bolt.new, you probably found out the wrong way. Not from a status page. From a customer saying something felt broken, or from noticing yourself that a project you were working on had quietly stopped responding. That gap, between when the tool goes down and when you personally realize it, is where the damage happens. A paying customer files a support ticket. A client loses confidence. You spend the first twenty minutes just confirming the problem is real and not something you did.
Why it is especially rough without a technical background
When you are not an engineer, there is nothing to read. No log file, no error trace, no red light on a server. The work just stops moving. A build stalls, a project does not load, and the screen gives you nothing useful. The first signal is often an unhappy person on the other end. By then you are already behind, already explaining yourself, already wishing you had known thirty minutes earlier.
Timeline
- 11:35 UTC - Bolt.new began experiencing a bigger problem.
- 13:35 UTC - Bolt.new reported the disruption resolved.
- Total duration - about 2 hours.
How a watcher catches this before your users do
NoCrash reads Bolt.new’s own public status page every minute. The moment that page flips from working to having trouble, NoCrash sends you a plain-language message. Not a raw status code. Not a vague alert. A sentence you can read and act on immediately, sitting next to everything else you build on.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those through your API token and surfaces a quiet stall before it becomes a customer complaint. If you have an app, you can give NoCrash a URL or drop in a small JS snippet, and it watches that too.
To be clear about what this is: NoCrash catches the trouble within a minute of Bolt.new’s own public report. It does not find the outage before Bolt.new knows about it. What it removes is the gap between Bolt.new posting an update and you personally seeing it, which on a busy day can be hours.
For the authoritative account of this outage, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.