What happened
Bolt.new had a significant outage starting July 8, 2026 at 17:05 UTC. It lasted about 7 hours and was resolved on July 9, 2026 at 01:01 UTC. Bolt.new has since reported the issue resolved, but has not published a detailed explanation of the cause.
Who this hits and how they usually find out
If you build on Bolt.new, your projects and workflows depend on it being available. When it goes quiet, nothing inside it tells you. No alert, no email, no red banner. You keep working, or you step away for the evening, and the problem sits there silently. The way most operators find out is a customer writes in asking why something is broken, or a client notices a project link is not loading. By then the outage has already been running for a while and you are scrambling to explain something you only just learned yourself.
Why this is especially rough without a technical background
If you are not an engineer, there is no log to pull up, no error trace to read. The work just stops moving and the screen looks normal. You might refresh a few times, wonder if it is your connection, and lose twenty minutes before you even suspect the tool itself is down. The first real signal is often an unhappy message from someone who paid you. That is a bad way to find out, and it puts you on the back foot immediately.
Timeline
- 17:05 UTC, July 8, 2026: Bolt.new began experiencing a bigger problem.
- About 7 hours of disruption while the issue persisted.
- 01:01 UTC, July 9, 2026: Bolt.new recovered and reported the issue resolved.
How a watcher catches this before your users do
Bolt.new, like most tools, maintains a public status page. When something goes wrong, they update it. The gap for most operators is that nobody is watching that page. NoCrash reads Bolt.new’s public status page every minute. The moment it flips from working to having trouble, NoCrash sends you a plain-language message telling you what is wrong, in words you can act on, without you having to go check anything. That turns “my customer told me at 10 PM” into “I got a calm heads-up at 17:06 and could tell my clients before they noticed.”
NoCrash also watches the 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 in one place.
To be clear about what this is: NoCrash reads the tool’s own public report. It does not find the outage before the tool knows about it. It just makes sure you hear about it right away, in plain English, instead of from a frustrated user.
For the authoritative account of this outage, see the official Bolt.new status page: https://status.bolt.new/proxy/status.bolt.new