On August 27, 2026, Bolt.new reported a bigger problem starting at 10:11 UTC. It lasted about two hours and was resolved at 12:14 UTC. Bolt.new has since confirmed the disruption is over.
Who this kind of outage hits
If you build on Bolt.new, you are probably not watching its status page while you work. Most people find out something went wrong the same way: a customer writes in, a client asks why their app is broken, or a collaborator says nothing is loading. By then the outage may already be over, but the damage to trust is done. The gap between “the tool stopped working” and “I found out” is almost always filled by someone who was not supposed to be your early warning system.
Why it is especially rough without a technical background
When a tool like Bolt.new goes quiet, there is no error message waiting for you. No log file, no alert, no red screen. Your work just stops moving. If you have automations or workflows running on top of it, those queue up silently. You might not notice for an hour. The first real signal is often a frustrated message from someone who paid you, which is the worst possible way to learn that something broke two hours ago.
What the timeline looked like
- 10:11 UTC - Bolt.new reported a bigger problem.
- 10:11 to 12:14 UTC - The disruption continued for about two hours.
- 12:14 UTC - Bolt.new confirmed the issue was resolved.
Bolt.new has not published a detailed explanation of the cause beyond confirming it is resolved.
How a watcher catches this before your users do
Bolt.new publishes a public status page. NoCrash reads that page every minute. The moment it flips from working to having trouble, NoCrash sends you a plain-language message, in words you can act on, without you having to check anything yourself. That is not the same as finding the problem before Bolt.new does. It means you hear about it within a minute of Bolt.new’s own report, instead of an hour later from a customer.
NoCrash also watches the things you ship. If you have n8n workflows running, it watches those. If you have an app with a URL or a small JS snippet, it watches that too. So a quiet stall on your own side surfaces alongside anything happening at the tool level. Everything sits in one place, described in plain English.
For the authoritative account of this outage, see the official Bolt.new status page: https://status.bolt.new/proxy/status.bolt.new