What happened
Bolt.new had a significant outage on July 23, 2026, starting at 15:37 UTC. It lasted about four hours and recovered at 19:54 UTC. Bolt.new has since reported the issue resolved. No detailed cause has been published at the time of writing.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, your work lives inside it. An outage like this one does not send you an email. It does not pop up a warning. The tool just stops doing what you expected, quietly, while you are doing something else. Most operators find out the wrong way: a customer writes in to say something is broken, or a client asks why their project has not moved. By then the outage may already be over, but the damage to trust is done. That gap between “the tool stopped working” and “I found out” is where the real cost lives.
Why this is especially rough if you are not an engineer
An engineer can pull logs, check error traces, and at least confirm that the problem is upstream. A non-engineer operator has none of that. The work just stops moving. There is no red screen, no message, nothing to screenshot and send to support. The first signal is often an unhappy person on the other end of a message thread. You then spend time ruling out whether it is your setup, your workflow, or something else entirely, before you even get to the point of checking whether the tool itself is having trouble. Four hours is a long time to be in that fog.
Timeline
- 15:37 UTC, July 23, 2026: Bolt.new began experiencing a bigger problem.
- About 4 hours of disruption while the issue persisted.
- 19:54 UTC, July 23, 2026: Bolt.new recovered and 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 saying what is wrong, in words you can act on, without you having to go check anything yourself. You find out within a minute of Bolt.new’s own public report, not an hour later when a customer writes in.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those too. If you give it a URL or add a small JS snippet to your app, it watches that as well. 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.
NoCrash does not find outages before the tool’s own status page does. It reads that page and tells you fast, in language that does not require a technical background to act on.
The authoritative account
For the official record of this outage, go to Bolt.new’s own status page: https://status.bolt.new/proxy/status.bolt.new