On October 16, 2026, Bolt.new reported a bigger problem starting at 15:09 UTC. It lasted about 12 minutes and was marked resolved at 15:22 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 short outage like this usually reaches you the wrong way. Not through an alert. Through a customer message, a confused reply to an email, or a support ticket that arrives an hour after the fact. By then you are already behind, already explaining, already apologizing for something you did not even know was happening. That gap, between the moment the tool stopped working and the moment you found out, is where the damage happens.
Why it is especially rough without a technical background
When a tool goes quiet, there is no error on your screen. No log to read. No red light. The work just stops moving and you have no way to know if it is your setup, your browser, or the tool itself. So you wait, or you start poking around, or you do nothing because you assume it will sort itself out. The first real signal is often an unhappy person on the other end of your product. That is a hard way to find out.
What the timeline looked like
- 15:09 UTC – Bolt.new reported a bigger problem
- 15:22 UTC – Bolt.new marked it resolved
- Total duration – about 12 minutes
Twelve minutes is short. But if a customer hit your app or your workflow during those 12 minutes, short does not feel short to them.
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. You find out within a minute of Bolt.new’s own report, not an hour later from a customer.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those too. If you have an app, you can give NoCrash a URL or drop in a small JS snippet and it will watch that as well. So a quiet stall on your own side surfaces the same way, in one place, in plain English.
NoCrash does not find outages before Bolt.new reports them. It reads what Bolt.new publishes and tells you immediately, in language that does not require a technical background to act on. That is the whole thing.
For the authoritative account of this outage, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.