What happened
Bolt.new had a significant disruption on July 24, 2026. It started at 11:12 UTC and lasted about 59 minutes, with the service recovering at 12:12 UTC. Bolt.new has since reported the issue resolved.
Who this hits and how they usually find out
If you build on Bolt.new, an hour of it going quiet can mean a project stalls, a client demo breaks, or a workflow that was supposed to run just stops. Most people who build on tools like this find out the same way: a customer writes in asking why something is broken, or a client mentions the app looks wrong, and only then does the builder go looking. By that point the outage may already be over, but the damage to trust is done. The tool itself rarely sends you a personal message when it has trouble. You have to already be watching.
Why this is especially rough without a technical background
If you are not an engineer, there is no log file to open, no error trace to read. The work just stops moving and the screen looks normal. A form does not submit. A build does not finish. An automation sits there. The first signal is often an unhappy person on the other end, not a clear message on your side. That gap, between when the tool stopped working and when you found out, is where the real cost lives.
Timeline
- 11:12 UTC, July 24, 2026 - Bolt.new begins experiencing a bigger problem.
- About 59 minutes of disruption - builds, projects, or workflows depending on Bolt.new would have been affected during this window.
- 12:12 UTC, July 24, 2026 - Bolt.new recovers and reports the issue resolved.
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. NoCrash reads that page every minute. The moment Bolt.new’s own status page flips from working to having trouble, NoCrash sends you a plain-language message saying what broke and when, in words you can act on without needing to interpret anything technical. That turns “my customer told me an hour later” into “I got a calm heads-up within a minute of Bolt.new’s own report.”
NoCrash also watches the things you ship. If you have n8n workflows, it watches those through your API token. If you have an app, it watches it through a URL you give it or a small JS snippet you drop in. So if the trouble is on your side rather than Bolt.new’s, that surfaces too, in the same place.
To be clear about what this is: NoCrash reads public status pages and watches the specific things you point it at. It does not find outages before the tool’s own status page does.
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