What happened
Bolt.new had a significant disruption on July 27, 2026. It started at 08:25 UTC and lasted about 42 minutes, recovering at 09:07 UTC. Bolt.new has since reported it resolved. That is the full picture the official source gives us right now.
Who this hits and how they usually find out
If you build on Bolt.new, you probably were not watching its status page at 8 in the morning. Most people are not. They are answering email, doing client calls, or just starting their day. The first sign something is wrong is usually a message from a customer: “hey, this isn’t working.” By then the disruption may already be over, but the damage to trust is done. You are now explaining something you did not know about, to someone who noticed before you did. That is a bad position to be in, and it happens constantly with third-party tools.
Why this is especially rough without a technical background
When a tool like Bolt.new has a bigger problem, there is no error on your screen. Nothing in your workflow says “I stopped because the platform is down.” The work just quietly stops moving. If you are not an engineer, there are no logs to pull, no alert to read, no way to tell whether the problem is on your side or theirs. You start second-guessing yourself. You wonder if you broke something. Meanwhile, your customers are hitting the same wall and drawing their own conclusions. The 42 minutes of disruption is one thing. The hour you spend figuring out what happened is another.
Timeline
- 08:25 UTC - Bolt.new’s bigger problem begins.
- 09:07 UTC - Bolt.new recovers. Total disruption: about 42 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 wrong and which tool it affects. You find out within a minute of Bolt.new’s own public report, not an hour later from a frustrated customer.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those too. If you give it a URL or add a small JS snippet to your app, it watches that as well. So if something goes quiet on your own side, that surfaces alongside anything happening on the tools you build on. Everything in one place, in words you can act on without needing to read a status page yourself.
To be straight about what it does not do: NoCrash does not find the outage before Bolt.new’s own status page does. It reads that page and tells you fast. That is the thing.
The official source
For the authoritative account of this disruption, go to Bolt.new’s own status page: https://status.bolt.new/proxy/status.bolt.new