On July 27, 2026, Bolt.new had a significant disruption starting at 16:40 UTC. It lasted about two hours and was resolved at 19:02 UTC. Bolt.new has since reported it as resolved, but has not published a detailed explanation of the cause.
Who this kind of outage hits
If you build on Bolt.new, you probably were not staring at a status page at 16:40 UTC. You were doing something else. The way most people find out about a problem like this is not from the tool itself. It is from a customer who tried to use something you built, got nothing, and sent you a message. That gap, between when the tool stopped working and when someone told you, is where the damage happens. A customer who hits a broken experience and hears nothing from you does not usually assume it is someone else’s fault.
Why this is especially rough without a technical background
When a tool like Bolt.new goes quiet, there is no error message sitting on your screen. There is no log file to open. The work just stops moving and you have no way to know whether the problem is on your side, the tool’s side, or somewhere in between. The first signal is often an unhappy person. By then you are already behind, explaining something you only just learned yourself.
What the timeline looked like
- 16:40 UTC - Bolt.new started having a bigger problem.
- About 2 hours - the disruption ran without a public resolution.
- 19:02 UTC - Bolt.new reported the issue resolved.
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, not a raw status code, not a link to a page you have to interpret. You get a calm heads-up sitting next to everything else you build on.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those too. If you have an app, you can give NoCrash a URL or drop in a small JS snippet and it will watch that as well. So if something goes quiet on your own side, that surfaces too, separately from what the tool is reporting.
To be clear about what this means in practice: NoCrash catches the trouble within a minute of Bolt.new’s own public report. It does not find the outage before Bolt.new does. What it does is make sure you are not the last to know.
The official source
For the authoritative account of this outage, go to Bolt.new’s own status page: https://status.bolt.new/proxy/status.bolt.new