What happened
Bolt.new reported a bigger problem on July 25, 2026, starting at 09:51 UTC. It lasted about 15 minutes and was marked resolved at 10:06 UTC. Bolt.new has since confirmed the issue is cleared.
Who this hits and how they usually find out
If you build on Bolt.new, a 15-minute window where things go wrong can still do real damage. A user tries to load something, gets nothing, and moves on. You find out later, when someone emails to say it was broken, or when you notice a drop in activity and start piecing it together. The tool itself rarely sends you a message saying “hey, something is wrong right now.” That gap, between the moment the trouble starts and the moment you hear about it, is almost always filled by a frustrated customer rather than an alert you chose to receive.
Why this is especially rough without a technical background
When you are not an engineer, there is no log file to open, no error trace to read. The work just stops moving. A build does not finish. A user hits a wall. Nothing on your screen explains why. The first real signal is often an unhappy message from someone who paid you, and by then the disruption is already in the past. You are left apologizing for something you did not know was happening.
Timeline
- 09:51 UTC, July 25, 2026 - Bolt.new’s status page showed a bigger problem beginning.
- About 15 minutes of disruption - the issue was active.
- 10:06 UTC, July 25, 2026 - Bolt.new marked 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 check anything yourself. For an outage like this one, that means you would have known within a minute of Bolt.new’s own report, instead of finding out from a user.
NoCrash also watches the things you ship. If you have n8n workflows, it watches those too. If you give it a URL or add a small JS snippet to your app, it watches that side as well. So if something goes quiet on your own side, that surfaces in the same place. One view, plain English, covering both the tools you build on and the things you put in front of users.
To be clear about what this is: NoCrash reads public status pages and watches the specific things you list. It does not find trouble before the tool’s own status page does. It just makes sure you hear about it right away, in plain language, rather than stumbling across it yourself.
The official source
For the authoritative account of this outage, see Bolt.new’s own status page at https://status.bolt.new/proxy/status.bolt.new.