What happened
Bolt.new had a bigger problem starting July 30, 2026 at around 17:50 UTC. It lasted about 19 hours, recovering on July 31 at 13:27 UTC. Bolt.new has since marked it resolved. No detailed cause has been published beyond that.
Who this hits and how they usually find out
If you build on Bolt.new, your projects, your automations, your whole workflow can go quiet without a single alert reaching you. The tool does not call you. It does not email you. Most operators find out the same way: a customer writes in asking why something is broken, or why nothing got delivered, or why the app looks wrong. By then the disruption has been running for hours. You are already behind, already apologizing, already trying to explain something you only just learned yourself.
That gap, between when the tool stopped working and when you found out, is where the damage happens. Not the outage itself. The silence around it.
Why this is especially rough without an engineering team
An engineer can pull logs, check error traces, see exactly when things went sideways. A solo operator or a small non-technical team has none of that. You open the tool and it looks fine, or it looks broken in a vague way, and there is nothing to read. The work just stops moving. No red screen, no clear message, just queued runs and confused customers. The first real signal is an unhappy person in your inbox, and by then you have already lost the window to get ahead of it.
Nineteen hours is a long time to be in the dark.
Timeline
- July 30, 2026, 17:50 UTC - Bolt.new reports a bigger problem beginning.
- July 31, 2026, 13:27 UTC - Bolt.new marks the issue resolved.
- Total duration - about 19 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, without you having to go check anything yourself. You find out within a minute of Bolt.new’s own report, not hours later when a customer beats you to it.
It also watches the things you ship. If you have n8n workflows, NoCrash 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 side, that surfaces as well, sitting next to everything else you build on.
To be straight about what this is: NoCrash reads what Bolt.new publishes about itself. It does not know about an outage before Bolt.new does. What it does is make sure you know as fast as Bolt.new’s own report allows, in plain English, in one place, instead of finding out from a frustrated customer.
The official source
For the authoritative account of this outage, go to Bolt.new’s own status page: https://status.bolt.new/proxy/status.bolt.new