On the night of August 10, 2026, Bolt.new ran into a bigger problem that lasted roughly one hour. It started at 22:04 UTC and was resolved by 00:01 UTC on August 11. Bolt.new has since reported the issue as resolved.
Who this kind of outage hits
If you build on Bolt.new, you probably found out about this one of two ways: you happened to be working at 10 pm UTC and noticed something felt wrong, or a customer told you the next morning. Most operators are not staring at their tools at that hour. The work just stops moving, quietly, and nothing sends you a message. That gap between “the tool stopped working” and “you found out” is where the damage happens.
The shape is always the same. A customer tries something, it fails, they wait a bit, they try again, it still fails, and then they email you. By the time you read that email, the outage is already over and you are left apologizing for something you did not even know about.
Why quiet outages are rough for non-engineers
There is no error screen to screenshot. There is no log file to open. The work just stops and the silence looks exactly like normal. A developer might notice a failed request in a console somewhere. A solo operator or a founder running automations has none of that. The first real signal is an unhappy customer, and by then you are already behind.
That is not a personal failure. It is just how these tools work. They do not call you when they have a problem.
What the timeline looked like
- 22:04 UTC, August 10 - Bolt.new began experiencing a bigger problem.
- About one hour of disruption - anything running on or through Bolt.new during this window was affected.
- 00:01 UTC, August 11 - Bolt.new recovered and has since reported 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 does not mean NoCrash finds the problem before Bolt.new does. It means you hear about it within a minute of Bolt.new’s own report, instead of hours later from a customer.
NoCrash also watches the things you ship. If you have n8n workflows, it watches those too. If you have an app, you can give it a URL or drop in a small JS snippet and it will watch that as well. So if something goes quiet on your side, that surfaces alongside anything going wrong on the tools you build on. Everything in one place, in plain English.
The goal is simple. “My customer told me” becomes “I got a calm heads-up first.”
For the authoritative account of this outage, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.