On the evening of October 22, 2026, Bolt.new reported a bigger problem starting at 19:58 UTC. It lasted about 12 minutes and was resolved by 20:11 UTC. Bolt.new has since confirmed the disruption is over. No detailed cause has been published.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, a short disruption like this one often goes completely unnoticed until something downstream breaks. A customer tries to use what you built, gets a blank screen or a broken flow, and sends you a message. That is usually the first signal. Not an alert, not a log, just an unhappy person wondering why your thing stopped working. By the time you see the message, the disruption may already be over, which makes it even harder to explain.
Why it is especially rough if you are not an engineer
There is nothing to read. No error on your screen, no red light in your builder, no queue of failed jobs you can point to. The work just stops moving. If your app or workflow depends on Bolt.new being healthy, a 12-minute gap can mean missed runs, broken user sessions, or a feature that silently did nothing. You find out when someone complains, not when the problem starts. That gap between “it broke” and “I knew it broke” is where trust with your users quietly erodes.
Timeline
- 19:58 UTC, October 22, 2026 - Bolt.new reports a bigger problem begins.
- 20:11 UTC, October 22, 2026 - Bolt.new reports the disruption is 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 check anything yourself. For a 12-minute disruption like this one, that means you could have known within a minute of Bolt.new’s own report, rather than finding out from a customer later.
NoCrash also watches the things you ship. If you have n8n workflows running, it watches those. If you have an app, it watches it 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.
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. What it does is make sure you hear about it right away, in plain English, in one place, instead of piecing it together from a customer complaint.
For the authoritative account of this disruption, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.