On October 23, 2026, Bolt.new had a significant disruption starting at 15:31 UTC. It lasted about 36 minutes and was resolved by 16:08 UTC. Bolt.new has since marked it resolved, but has not published a detailed cause.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, you are probably using it to spin up apps, prototype features, or hand off working code to clients. When the tool goes quiet, none of that moves. The problem is that nothing inside Bolt.new sends you a message saying “we are having trouble right now.” You are just sitting there wondering if it is your browser, your connection, or something you did. Most people find out the real way: a client pings them, a customer hits a broken link, or someone on a call asks why the thing you promised is not working. By then you are already behind.
Why this is especially rough if you are not an engineer
There are no logs to read. There is no error message that explains anything useful. The work just stops, silently, and the first real signal is often an unhappy person on the other end. An engineer might check a status page out of habit. A solo founder or automation operator usually does not, because there are twelve other things open and nothing on the screen is screaming at them. The gap between “the tool stopped working” and “I found out” can be an hour or more, and that whole time you look unresponsive to whoever is waiting on you.
Timeline
- 15:31 UTC - Bolt.new began experiencing a bigger problem.
- 15:31 to 16:08 UTC - The disruption continued for about 36 minutes.
- 16:08 UTC - Bolt.new resolved the issue and updated their status page.
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. That turns “my client just told me something is broken” into “I got a heads-up 36 minutes ago and already knew.” It does not find the outage before Bolt.new’s own status page does, it catches the change within a minute of Bolt.new’s own report. NoCrash also watches the things you ship: your n8n workflows through an API token, and your app through a URL or a small JS snippet you add. So if your own side goes quiet separately, that surfaces too, all in one place.
For the authoritative account of this outage, see the official Bolt.new status page: https://status.bolt.new/proxy/status.bolt.new