Bolt.new had a bigger problem starting August 6, 2026 at around 15:11 UTC. It lasted close to two full days, recovering on August 9 at 02:36 UTC. Bolt.new has since marked it resolved.
Who this hits and how they usually find out
If you build on Bolt.new, your projects, your prototypes, your client work all live inside it. When it goes down hard, nothing you hand off works the way it should. The people who find out first are usually not you. They are your client clicking a link, your user trying to load something, your customer sending a message that says “is this broken?” That gap, between when the tool stopped and when someone told you, is where the damage happens. You were not ignoring it. You just had no way to know.
Why this is especially rough without a technical background
A quiet outage gives you nothing to read. No error on your screen, no alert in your inbox, no log file to open. The work just stops moving. If you have automations or workflows running through Bolt.new, they go silent. If you have something built on it that customers use, it goes dark. The first signal is an unhappy person on the other end, and by then you are already behind. You are explaining something you only just learned yourself.
What the timeline looked like
Bolt.new started showing a bigger problem on August 6, 2026 at 15:11 UTC. The disruption ran for roughly two days. It cleared on August 9, 2026 at 02:36 UTC. That is a long window for anything customer-facing to be broken without a heads-up.
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. Not a status code, not a raw alert. Something you can read and act on immediately, sitting next to everything else you build on.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those too. If you have an app or a page you want watched, you give it a URL or drop in a small JS snippet and it keeps an eye on that as well. So if something goes quiet on your own side, that surfaces alongside anything happening upstream.
To be straight about what this is: NoCrash does not find the outage before Bolt.new’s own status page does. It reads that page and tells you within a minute of Bolt.new’s own report, in words you can act on, without you having to go check anything yourself. The difference is “my customer told me two hours later” versus “I got a calm heads-up the moment Bolt.new flagged it.”
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