On June 29, 2026, Bolt.new experienced a significant disruption starting at 13:40 UTC. It lasted about 35 minutes and was resolved by 14:15 UTC. Bolt.new has since confirmed the issue is resolved, though no detailed cause has been published.
Who this kind of outage hits
If you build or ship something on Bolt.new, a 35-minute window where the tool is having a bigger problem can quietly swallow a chunk of your working day. Most people find out the wrong way: a customer messages them, a collaborator says something feels broken, or they notice a project just stopped moving. By then the disruption is already over, but the damage to trust is done. There is no alert inside Bolt.new that says “hey, we are struggling right now.” You are just left wondering whether the problem is you or them.
Why this is especially rough if you are not an engineer
There is no log to read. There is no red error on the screen. The work just stops, quietly, and you have no way to know if it is your internet, your browser, your project, or the platform itself. So you spend time troubleshooting things that are not broken. Then a customer asks why something is not working, and you have to explain an outage you only just found out about yourself. That is a bad position to be in, and it happens constantly with tools that do not surface their own trouble clearly.
Timeline
- 13:40 UTC - Bolt.new begins experiencing a bigger problem.
- 14:15 UTC - Bolt.new recovers. Total disruption: about 35 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 plain English, telling you what is going on. You do not have to check the status page yourself. You do not have to wait for a customer to tell you.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those too. If you have an app, you can give it a URL or drop in a small JS snippet, and NoCrash will watch that as well. So if something goes quiet on your own side, that surfaces alongside anything happening on the tools you build on.
To be clear about what this is: NoCrash catches the trouble within a minute of Bolt.new’s own public report. It does not find the outage before Bolt.new knows about it. What it does is make sure you hear about it in plain language, fast, in one place, instead of finding out from a frustrated user.
For the authoritative account of this outage, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.