On August 12, 2026, Bolt.new reported a bigger problem starting at 13:55 UTC. It lasted about four hours and was resolved at 18:08 UTC. Bolt.new has since confirmed the disruption is over.
Who this kind of outage hits
If you build or run something on Bolt.new, a four-hour window where the tool is struggling is not a small thing. Most people find out the wrong way: a customer messages them, a client asks why nothing is working, or a form submission just quietly vanishes. There is no alarm. There is no pop-up. The tool goes quiet and the work stops moving, and the first signal is someone else’s frustration landing in your inbox.
Why it is especially rough if you are not an engineer
When a tool you depend on has trouble, an engineer can pull logs, check error outputs, and at least feel like they are doing something. If you are a solo founder or an automation operator, none of that is available to you. The screen looks normal. The workflow looks fine. But nothing is actually running. You find out hours later, sometimes days later, when a customer asks why their order confirmation never arrived or why the thing you promised them did not happen. That gap between “it broke” and “I found out” is where trust gets damaged.
Timeline
- 13:55 UTC Bolt.new’s status page showed a bigger problem.
- The disruption ran for about four hours.
- 18:08 UTC Bolt.new marked the issue resolved.
Bolt.new has not published a detailed explanation of what caused this. The official source is the place to watch for any further updates.
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 telling you what is wrong, in words you can act on, without you having to go check anything yourself. That is the difference between “my customer told me at 5pm” and “I got a heads-up at 1:55pm and could at least set expectations.”
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 can give NoCrash a URL or drop in a small JS snippet and it will watch that as well. So a quiet stall on your own side surfaces the same way, in the same place, in plain English.
To be clear about what NoCrash does not do: it 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. That is the honest version of what it offers.
For the authoritative account of this outage, go to the official Bolt.new status page: https://status.bolt.new/proxy/status.bolt.new