What happened
Bolt.new had a significant disruption on July 25, 2026. It started at 18:45 UTC and lasted about an hour, recovering at 19:47 UTC. Bolt.new has since reported it 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, you are probably not watching its status page while you work. Most people find out something broke when a customer writes in, or when they sit down the next morning and notice nothing came through. That gap, between when the tool stopped working and when you heard about it, is where the damage happens. A client asks why their project stalled. You have no answer ready because you did not know.
Why this is especially rough if you are not an engineer
There is no error on your screen. No alert. The work just quietly stops moving. If you are running automations or builds on top of Bolt.new, they do not shout when they stall. They go silent. The first real signal is often an unhappy person on the other end wondering why nothing happened. By then you are already behind, already explaining, already apologizing for something that was not your fault and that you had no way to see coming.
Timeline
- 18:45 UTC, July 25, 2026 - Bolt.new begins experiencing a bigger problem.
- About 1 hour - the disruption continues with no recovery.
- 19:47 UTC, July 25, 2026 - Bolt.new recovers and reports 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. 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.”
It also watches the things you ship. If you have n8n workflows, NoCrash watches those through your API token. If you have an app, you can give it a URL or drop in a small JS snippet, and it watches that too. So if something goes quiet on your own side, that surfaces alongside anything happening with the tools underneath it. Everything sits in one place, in plain English.
NoCrash does not find outages before the tool’s own status page does. It reads what Bolt.new publishes, as fast as it publishes it, and tells you in language you can actually use.
For the authoritative account of this outage, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.