Bolt.new had a significant disruption on October 16, 2026. It started at 05:54 UTC and lasted about an hour, recovering at 07:24 UTC. Bolt.new has since reported it resolved. No detailed cause has been published.
Who this kind of outage hits
If you build or ship something on Bolt.new, an hour of it not working properly can mean projects stall, builds fail quietly, or work you expected to be done simply is not. The hard part is that nothing usually tells you. You are not watching a server. You are just waiting for something to finish, and when it does not, the first person to notice is often a client or a user asking why their thing is broken. That gap, between when the tool went wrong and when someone told you, is where the damage happens.
Why it is rough without a technical background
If you are not an engineer, there is no log file to open, no error message pointing at the real problem. The work just stops moving. You might refresh, try again, wonder if you did something wrong. By the time it is clear the problem is on Bolt.new’s side and not yours, you may have already sent an apologetic message to someone who was counting on you. The outage itself is one thing. The not-knowing is what makes it costly.
What the timeline looked like
- 05:54 UTC - Bolt.new started experiencing a bigger problem.
- ~06:54 UTC - About one hour in, the disruption was still active.
- 07:24 UTC - Bolt.new recovered. Total duration: about one hour and thirty 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, without you having to go check anything yourself. That is the difference between hearing about it from a frustrated user and getting a calm heads-up first, so you can set expectations before anyone asks.
NoCrash also watches the things you ship. If you have n8n workflows running, it watches those too. If you have an app or a URL you care about, you can give NoCrash that URL or add a small JS snippet, and it will watch that as well. So if the problem is on Bolt.new’s side, you hear about it from their status page. If the problem is on your own side, that surfaces too.
For the authoritative account of this outage, see Bolt.new’s official status page: https://status.bolt.new/proxy/status.bolt.new