On the evening of July 7, 2026, Bolt.new had a significant problem starting at 20:20 UTC. It lasted about three hours and was resolved at 23:47 UTC. Bolt.new has since reported it as resolved. The cause has not been published in detail.
Who this kind of outage hits
If you build on Bolt.new, you are probably not watching its status page while you work. Most people are not. So when something goes wrong, the first signal is usually a customer writing in to say something is broken, or a collaborator asking why nothing is loading. That gap, between the moment the tool stops working and the moment you find out, is where the damage happens. A few hours of quiet failure can mean a full day of cleanup.
Why it is especially rough if you are not an engineer
There is no error on your screen. There is no log to read. The work just stops moving and you do not know if it is you, your setup, or the tool itself. You start second-guessing your last change. You ask around. Meanwhile, customers are hitting the same wall and drawing their own conclusions. By the time you confirm it was a platform problem, you are already behind on the explanation.
What the timeline looked like
- 20:20 UTC - Bolt.new started having a bigger problem.
- 20:20 to 23:47 UTC - The disruption ran for about three hours.
- 23:47 UTC - Bolt.new reported the issue resolved.
How a watcher catches this before your users do
Bolt.new, like most tools, publishes a public status page. NoCrash reads that page every minute. The moment it flips from working to having trouble, NoCrash sends you a plain-language message, in words you can act on, without you having to go looking. That means instead of hearing it from a customer, you hear it from a calm heads-up that arrives within a minute of Bolt.new’s own report.
NoCrash also watches the things you ship. If you have n8n workflows, it watches those too. If you give it a URL or drop in a small JS snippet, it watches your app directly. So if the problem is on your side rather than Bolt.new’s side, that surfaces as well. It does not replace Bolt.new’s own status page. It just means you do not have to remember to check it.
For the authoritative account of this outage, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.