Bolt.new had a bigger problem starting July 31, 2026 at around 15:25 UTC. It lasted about 23 hours, recovering on August 1 at around 15:20 UTC. Bolt.new has since marked it resolved. No detailed cause has been published.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, a 23-hour disruption is not a blip. It is a full working day where projects stall, builds do not go through, and anything you promised a client sits frozen. The way most people find out is not from a system alert. It is from a customer asking why their thing is broken, or from a teammate saying “hey, is something wrong?” by which point the damage is already done. You were the last to know, and the first to apologize.
That gap, between when the tool stopped working and when you heard about it, is where the real cost lives.
Why this is especially rough without an engineering team behind you
A developer at a big company has colleagues, internal tools, and someone whose job is to watch for this stuff. A solo operator or a small team building on Bolt.new has none of that. There is no error on your screen. There is no log file to open. The work just stops moving, quietly, and the first signal is an unhappy customer or a missed deadline. You spend the first hour wondering if you did something wrong. You spend the second hour trying to reproduce it. By hour three you find the status page, and by then you have already lost time you cannot get back.
Timeline
- July 31, 2026, 15:25 UTC: Bolt.new begins reporting a bigger problem.
- About 23 hours of disruption follow, covering the rest of July 31 and most of August 1.
- August 1, 2026, 15:20 UTC: 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 is not the same as finding the outage before Bolt.new knows about it. It is not. What it does is make sure you hear about it within a minute of Bolt.new’s own report, instead of hearing about it from a customer hours later.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those too. If you give it a URL or drop in a small JS snippet, it watches your app directly. So if the problem is on your side rather than Bolt.new’s side, that surfaces as well. Everything sits in one place, in plain English, without you having to check five different pages.
The difference is not magic. It is just that the information reaches you first, calmly, before someone else’s frustration does.
For the authoritative account of this outage, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.