On the evening of October 12, 2026, Bolt.new reported a bigger problem starting at 20:18 UTC. It lasted about 23 minutes and was resolved by 20:42 UTC. Bolt.new has since confirmed the issue is resolved. That is the full picture the official record gives us right now.
Who this kind of outage hits and how they usually find out
If you build on Bolt.new, a 23-minute disruption can quietly swallow a chunk of work with no warning inside the tool itself. The shape is always the same: you are not watching the status page, your workflow stalls or your app goes quiet, and the first signal you get is a customer asking why something is broken. By then the outage may already be over, but the damage to trust is done. Most people find out from a user, not from the tool.
Why this is especially rough if you are not an engineer
There is no error on your screen. There is no log to read. The work just stops moving, or the app stops responding, and nothing tells you why. You start second-guessing yourself. You wonder if you broke something. You spend time checking your own setup before it even occurs to you to check whether the tool itself is having trouble. That gap, between the moment something goes wrong and the moment you understand it is not your fault, is where the real cost lives.
Timeline
- 20:18 UTC Bolt.new reports a bigger problem begins.
- 20:42 UTC Bolt.new reports the issue is resolved.
- Total duration: about 23 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 immediately, without you having to go find it yourself. That turns “my customer just told me something is broken” into “I got a heads-up within a minute of Bolt.new’s own report.” It also watches the specific things you ship: your n8n workflows through an API token, and your app through a URL you give it or a small JS snippet you drop in. So if something goes quiet on your own side, that surfaces too, sitting next to everything else you build on. It does not find the outage before Bolt.new’s own status page does. It just makes sure you hear about it right away, in plain English, in one place.
For the authoritative account of this outage, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.