On July 27, 2026, Bolt.new experienced a significant disruption starting at 13:45 UTC. It lasted about 52 minutes and was resolved by 14:37 UTC. Bolt.new has since reported the issue as resolved, but has not published a detailed cause.
Who this kind of outage hits
If you build on Bolt.new, you probably found out about this the hard way. Someone tried to use something you shipped, it did not work, and they told you. That is the usual shape of it. The tool goes quiet, nothing on your screen changes, and the first signal is a message from a customer or a collaborator asking why things are broken. By the time that message arrives, the disruption may already be half over, but the damage to trust is done.
Why it is especially rough without a technical background
When a tool you build on stops working, there is nothing to read. No log file, no error message with a clear cause, no red light on a screen you own. The work just stops moving. If you are running automations, they queue up silently or fail without a trace. If you are showing a client something, it simply does not load. You start second-guessing yourself, wondering if you broke something, before you even know the tool itself is the problem. That gap between “something is wrong” and “I know what is wrong” is where the stress lives.
Timeline
- 13:45 UTC - Bolt.new begins experiencing a bigger problem.
- 14:37 UTC - Bolt.new reports the issue resolved.
- Total duration - about 52 minutes.
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 yourself. That turns “my customer just told me” into “I got a heads-up 52 minutes ago and already knew.”
It also watches the things you ship. If you have n8n workflows, NoCrash watches those through your API token. If you have an app or a page, you can give NoCrash a URL or drop in a small JS snippet and it will watch that too. 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 tools.
NoCrash does not find outages before the tool’s own status page does. It reads that page and tells you quickly, in plain English, the moment the tool itself reports trouble.
For the authoritative account of this outage, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.