Bolt.new had a significant disruption on July 26, 2026, starting just after 01:04 UTC. It lasted about 42 minutes and was resolved by 01:46 UTC. Bolt.new has since reported the issue as resolved.
Who this kind of outage hits
If you build or ship on Bolt.new, a 42-minute window where the tool has a bigger problem can mean projects stall, builds stop, and anyone you handed a link to hits a wall. The hard part is that nothing inside your workflow sends you a message. You are not sitting there watching a status page at 1 in the morning. You find out when a client emails to say something is broken, or when you check in the next morning and realize work that should have finished never did. That gap between “it broke” and “you knew” is where the damage happens.
Why this is rough without a watcher
There is no error on your screen. There is no log to read. The work just quietly stops moving, and the first signal is an unhappy person asking why their thing does not work. For a non-engineer operator, that is the worst shape for bad news to arrive in, because by the time you hear it you are already behind. You have to explain something you did not know about, to someone who noticed before you did.
Timeline
- 01:04 UTC, July 26, 2026 - Bolt.new begins reporting a bigger problem.
- 01:46 UTC, July 26, 2026 - Bolt.new reports the issue resolved.
- Total duration - about 42 minutes.
How a watcher catches this before your users do
Bolt.new, like most tools, publishes a public status page. When something goes wrong, they update it. The gap for most operators is that nobody is reading that page every minute at 1 AM.
NoCrash reads Bolt.new’s public status page every minute. The moment it flips from working to having trouble, NoCrash sends you a plain-language heads-up in words you can act on, sitting next to everything else you build on. You are not faster than Bolt.new’s own report, but you are as fast as it gets after that, without having to watch anything yourself.
NoCrash also watches the things you ship. If you have n8n workflows, it watches those too. If you have an app, you can give it a URL or drop in a small JS snippet and it will watch that as well. So if the trouble is on your side rather than Bolt.new’s side, that surfaces too. The result is that “my customer told me” becomes “I got a calm heads-up first.”
For the authoritative account of this outage, see the official Bolt.new status page: https://status.bolt.new/proxy/status.bolt.new