On the night of July 17, 2026, Bolt.new reported a bigger problem starting at 23:15 UTC. It lasted about 12 minutes and was marked resolved at 23:28 UTC. Bolt.new has since confirmed the disruption is over. No detailed cause has been published.
Who this kind of outage hits
If you build on Bolt.new, a short disruption like this one rarely announces itself. There is no alert inside the tool, no email, no pop-up. You find out when a customer tries something and it does not work, or when you check in yourself and notice things have gone quiet. Twelve minutes is short, but if a customer hit that window and got nothing back, the first you heard of it was probably from them, not from Bolt.new.
Why it is especially rough without a technical background
When you are not an engineer, a quiet outage is the hardest kind. There are no logs to read. Nothing on your screen says “the tool is down.” The work just stops moving, and you have no way to know whether the problem is on your side or theirs. So you start second-guessing yourself, checking settings, maybe even apologizing to a customer for something that was never your fault. The first real signal is an unhappy message, and by then the disruption may already be over, which makes it even harder to explain.
Timeline
- 23:15 UTC, July 17, 2026 - Bolt.new reports a bigger problem begins.
- 23:28 UTC, July 17, 2026 - Bolt.new marks the disruption resolved.
- Total duration - about 12 minutes.
How a watcher catches this before your users do
Bolt.new publishes a public status page. NoCrash reads that page every minute. The moment it 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 just told me something is broken” into “I got a heads-up a minute after Bolt.new’s own page reported it.”
NoCrash also watches the things you ship. If you have n8n workflows running, it watches those too. If you give it a URL or drop in a small JS snippet for your app, it watches that side as well. So a quiet stall on your own side surfaces the same way, in the same place, without you having to check two or three different places.
To be clear about what this is: NoCrash reads Bolt.new’s own public status page. It does not find the outage before Bolt.new reports it. It just makes sure you hear about it right away, in plain English, instead of from a frustrated user.
For the authoritative account of this disruption, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.