On the evening of July 29, 2026, Bolt.new had a significant disruption. It started at 19:55 UTC and lasted roughly two hours, with Bolt.new reporting it resolved at 22:22 UTC. The official status page now shows the issue is cleared.
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. You are building, or you are away from your desk. The first sign something is wrong is often a message from a customer asking why their project is broken, or why nothing is saving, or why the app they just paid for looks frozen. That gap, between when the tool stopped working and when you heard about it, is where the damage happens. A two-hour window is long enough for a customer to lose trust, ask for a refund, or just quietly leave.
Why this is especially rough if you are not an engineer
There is no error on your screen. Nothing crashes in a dramatic way. The work just stops moving. If you are running automations or shipping something built on Bolt.new, the silence looks exactly like normal. You have no logs to check, no alert to read. The first real signal is a confused or unhappy person on the other end. By then you are already behind, explaining something you did not know was happening.
Timeline
- 19:55 UTC, July 29, 2026: Bolt.new begins reporting a bigger problem on its status page.
- About 2 hours of disruption while the issue was active.
- 22:22 UTC, July 29, 2026: Bolt.new marks 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 looking. That turns “my customer just told me something is broken” into “I got a heads-up an hour and a half ago and could say something first.”
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 NoCrash watches that too. So if the problem is on your side rather than Bolt.new’s side, that surfaces as well. What it does not do is detect an outage before Bolt.new’s own status page reports it. The speed comes from reading that page every minute and telling you immediately, not from any independent probing of Bolt.new’s systems.
For the authoritative account of this outage, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.