On July 25, 2026, Bolt.new reported a bigger problem starting at 14:20 UTC. It lasted about seven minutes and was marked resolved at 14:27 UTC. Bolt.new has since confirmed the disruption is over. The cause has not been published in detail.
Who this kind of outage hits
If you build on Bolt.new, a short outage like this usually lands silently. Nothing pings you. No email arrives. You find out because a customer tries something, it fails, and they write to you. By then the tool may already be back, but the damage to trust is done. Seven minutes is short enough that many operators never even knew it happened, which sounds like good news until a customer tells you their project stalled mid-session and they assumed it was your fault.
Why it is especially rough without a technical background
When a tool you build on goes quiet, there is no log to read, no error on your screen, no obvious place to look. The work just stops moving. If you are not an engineer, you have no way to tell whether the problem is on Bolt.new’s side, your own setup, or something else entirely. So you wait, or you start second-guessing your own product, or you spend an hour ruling things out before someone mentions they checked the status page. That hour costs you.
A short timeline
- 14:20 UTC, July 25, 2026 - Bolt.new reports a bigger problem begins.
- 14:27 UTC, July 25, 2026 - Bolt.new marks the disruption resolved.
- Total duration - about 7 minutes.
How a watcher catches this before your users do
Bolt.new publishes a public status page. NoCrash reads that page every minute. The moment it flips from working to having trouble, NoCrash sends you a plain-language message, in words you can act on, without you having to think about what the status page actually means. For a seven-minute outage like this one, that means you could know within a minute of Bolt.new’s own report, instead of finding out from a frustrated user later.
NoCrash also watches the things you ship. If you have n8n workflows running, it watches those too. If you give it a URL or drop in a small JS snippet, it watches your app directly. So if something goes quiet on your own side, that surfaces in the same place. One message, plain English, before your customers notice.
To be clear about what this is: NoCrash reads what Bolt.new publishes. It does not find the outage before Bolt.new reports it. It just makes sure you hear about it right away, in plain language, without having to watch a status page yourself.
For the authoritative account of this outage, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.