On June 24, 2026, Bolt.new experienced a significant disruption starting at 13:20 UTC. It lasted roughly one hour, recovering at 14:57 UTC. Bolt.new has since reported the issue resolved.
Who this kind of outage hits
If you build apps or prototypes on Bolt.new, a disruption like this stops your work cold. The harder problem is that nothing inside Bolt.new sends you a message when it goes wrong. You are usually mid-project, or you have handed something to a client, and the first sign anything is broken is a confused reply from them. “It’s not loading.” “I can’t get in.” That message arrives minutes or hours after the trouble started, and by then you are already behind.
Most people who build on tools like this are not watching a wall of logs. They are doing five other things. The outage happens quietly, in the background, and the only early-warning system is a paying customer who is annoyed enough to say something.
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. Your project just stops responding, or a feature stops working, and it is not obvious whether the problem is on your end or theirs. You refresh. You try a different browser. You wonder if you broke something. That loop costs real time, and it ends the same way: you eventually find the status page yourself, or someone tells you. There are no logs to read, no alert to dismiss. The work just stops moving.
Timeline
- 13:20 UTC, June 24, 2026 - Bolt.new begins experiencing a bigger problem.
- About 1 hour - the disruption runs.
- 14:57 UTC, June 24, 2026 - Bolt.new reports 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 words you can act on, without you having to go looking. That is the gap it closes: not the outage itself, but the time between the tool’s own report and the moment you find out.
It also watches the things you ship. If you give NoCrash a URL for your app, or add a small JS snippet, it watches that too. Same with n8n workflows, through an API token. So if something goes quiet on your own side, that surfaces alongside anything happening with the tools underneath it. Everything in one place, in plain English.
To be clear 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 quickly. The speed comes from checking every minute and translating the result into something human, not from any special access.
The authoritative account
For the official record of this outage, go to Bolt.new’s status page directly: https://status.bolt.new/proxy/status.bolt.new