What happened
Bolt.new had a significant outage on July 18, 2026, starting at 03:00 UTC and lasting about one hour. It recovered at 04:00 UTC. Bolt.new has since reported the issue resolved. The details of what went wrong have not been published beyond that.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, your projects, your prototypes, your whole workflow can go quiet without a single alert reaching you. Most people find out the wrong way: a client emails asking why something is broken, or a customer tries to use what you shipped and gets nothing. By then the outage is already over, but the damage to trust is done. The tool never sent you a message. You were just the last to know.
Why this is especially rough if you are not an engineer
There is no error log to open. There is no red light on a screen. The work just stops, silently, and you have no way to know whether the problem is on Bolt.new’s side, your side, or somewhere in between. So you wait, or you start second-guessing yourself, or you find out from an unhappy customer at 9 a.m. That is the shape of a quiet outage for a solo operator: not a dramatic crash, just a gap where work should have been, discovered too late.
Timeline
- 03:00 UTC, July 18, 2026 - Bolt.new begins experiencing a bigger problem.
- 03:00 to 04:00 UTC - The disruption continues for approximately one hour.
- 04:00 UTC - Bolt.new recovers and reports the issue resolved.
How a watcher catches this before your users do
Bolt.new, like most tools, publishes a public status page. When something goes wrong, they update it. The gap for most operators is that nobody is reading that page at 3 a.m.
NoCrash reads Bolt.new’s public status page every minute. The moment it flips from working to having a problem, NoCrash sends you a plain-language message, in words you can act on, without you having to go looking. That turns “my customer told me at 9 a.m.” into “I got a calm heads-up at 3:01 a.m.” It also watches the specific things you ship: your n8n workflows through an API token, and your app through a URL you give it or a small JS snippet you drop in. So if something goes quiet on your own side, that surfaces too, sitting next to everything else you build on.
To be clear about what this is: NoCrash catches the trouble within a minute of Bolt.new’s own public report. It does not find the outage before Bolt.new knows about it. It just makes sure you hear about it in plain English, fast, instead of from a frustrated user.
For the authoritative account of this outage, see Bolt.new’s official status page at https://status.bolt.new/proxy/status.bolt.new.