On July 24, 2026, Bolt.new had a significant disruption starting at 18:40 UTC. It lasted about 50 minutes and was resolved by 19:30 UTC. Bolt.new has since reported the issue as resolved. The cause has not been detailed publicly.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, a 50-minute disruption in the early evening can quietly swallow a chunk of work. Builds stall, previews stop loading, and nothing inside the tool tells you why. The way most people find out is not from Bolt.new, and not from a status page they happened to check. It is from a client asking why the thing they were just shown is broken, or from a collaborator asking why nothing is updating. By the time that message arrives, the disruption may already be half over, but the damage to trust is done.
Why this is especially rough if you are not an engineer
There is no error log to read. There is no red warning on your screen. The work just stops moving. You might refresh a few times, wonder if it is your connection, try a different browser, and lose ten minutes before you even suspect the tool itself is the problem. Then you check the status page, and sure enough, something is wrong. But you found out last. Your customer, or your client, or the person you demo’d to this afternoon, found out first.
That gap, between when the tool starts having trouble and when you personally know about it, is where the stress lives.
Timeline
- 18:40 UTC – Bolt.new begins experiencing a bigger problem.
- 19:30 UTC – Bolt.new reports the issue resolved.
- Total duration – about 50 minutes.
How a watcher catches this before your users do
Bolt.new publishes a public status page. The moment that page flips from working to having trouble, NoCrash picks it up, within a minute of Bolt.new’s own report, and sends you a plain-language message. Not a raw status code. Not a technical alert you have to decode. Just a calm note that says something is wrong, in words you can act on immediately.
NoCrash also watches the things you ship. If you have n8n workflows running, 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 trouble is on your side rather than Bolt.new’s side, that surfaces as well.
To be straight about what this is: NoCrash reads public status pages and watches the specific things you point it at. It does not find the outage before Bolt.new’s own status page does. What it does is make sure you are not the last to know.
The authoritative account
For the official record of this outage, go to Bolt.new’s status page: https://status.bolt.new/proxy/status.bolt.new