What happened
Bolt.new had a significant disruption on October 6, 2026. It started at 08:38 UTC and was resolved by 09:57 UTC, lasting about one hour. Bolt.new has since reported the issue resolved, with no detailed cause published at this time.
Who this kind of outage hits and how they usually find out
If you build on Bolt.new, you are probably using it to generate, iterate, or ship something fast. An hour of it not working properly means work stops, queues up, or produces nothing quietly. The people who feel that first are often not you. They are your users, your clients, or someone waiting on a deliverable. The typical shape is: you find out because someone messages you asking why something is broken, and only then do you go looking. By that point the outage may already be over, but the damage to trust is done.
Why this is especially rough if you are not an engineer
There is no error log to open. There is no alert on your screen. The work just stops moving, and nothing tells you why. If you have an n8n workflow that calls Bolt.new, the runs may queue silently or fail without a clear message. If your app depends on it, your users hit a wall and you are the last to know. The first signal is an unhappy customer, a confused client, or a missed deadline. That is a hard position to recover from, and it happens not because you did anything wrong but because the tool went quiet and nothing told you.
Timeline
- 08:38 UTC - Bolt.new starts showing a bigger problem.
- 09:57 UTC - Bolt.new reports the issue resolved.
- Total duration - about 1 hour.
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 customer told me something is broken” into “I got a heads-up an hour ago and already knew.”
It also watches the things you ship. If you have n8n workflows, NoCrash watches them through your API token, so a quiet stall on your own side surfaces 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. The point is one place, plain English, before your users notice.
What NoCrash does not do: it does not find the outage before Bolt.new’s own status page does. It reads that page and tells you fast. That is the honest version of what it is.
The authoritative account
For the official record of this outage, go to Bolt.new’s status page directly: https://status.bolt.new/proxy/status.bolt.new