On the morning of July 20, 2026, Bolt.new reported a bigger problem starting at 07:10 UTC. The disruption lasted about three hours. By 10:58 UTC, Bolt.new reported it resolved. The status note says nothing more specific than that, so neither do we.
Who this kind of outage hits
If you build on Bolt.new, you probably found out the wrong way. Not from a status page. From a customer asking why something is broken, or from a colleague wondering why a project link stopped loading. That gap, between when the tool stopped working and when you heard about it, is where the damage happens. A paying customer forms an opinion about your reliability before you even know there is a problem to fix.
Why it is especially rough without a technical background
When a tool like Bolt.new goes quiet, there is no error message waiting for you. No log file, no alert, no red screen. The work just stops moving. If you are not an engineer, you have no obvious place to look. You might refresh the page a few times, wonder if it is your internet connection, and lose twenty minutes before you even suspect the tool itself is the problem. By then, someone else has already noticed.
That is the shape of a quiet outage for a non-engineer operator. The first signal is almost always a frustrated user, not a system alert.
Timeline
- 07:10 UTC Bolt.new’s status page showed a bigger problem.
- ~10:58 UTC Bolt.new marked the disruption resolved.
- Total duration: about 3 hours.
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 immediately, without translating any technical language. That means you hear about it within a minute of Bolt.new’s own report, not an hour later when a customer emails you.
It also watches the things you ship on top of Bolt.new. If you have n8n workflows running, NoCrash watches those too. If you give it a URL or drop in a small JS snippet for your app, it watches that as well. So a quiet stall on your own side surfaces alongside anything happening at the tool level, all in one place.
NoCrash does not find outages before the tool’s own status page does. No tool can. What it does is make sure you are not the last to know once the tool has reported something.
For the authoritative account of this outage, go to Bolt.new’s official status page: https://status.bolt.new/proxy/status.bolt.new