What happened
Bolt.new had a significant disruption on August 13, 2026, starting at 14:40 UTC. It lasted about three hours and was resolved at 18:02 UTC. Bolt.new has since confirmed the issue is resolved. The details of what caused it have not been published beyond that.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, your projects, your automations, your whole workflow can quietly stall the moment the tool has trouble. The problem is that nothing inside Bolt.new sends you a message saying “hey, things are broken right now.” So the first signal most people get is a customer writing in to ask why something is not working, or a collaborator saying they cannot access the project. By that point, the disruption has already been running for an hour or two. You are now explaining a problem you did not know you had.
That gap, between when the tool stopped working and when you found out, is where the real damage happens. Not the outage itself, but the silence around it.
Why this is especially rough if you are not an engineer
An engineer can go looking for logs, check error outputs, dig into what broke. A solo founder or automation operator does not have that. The work just stops moving. No red screen, no alert, no message. A form stops submitting, a workflow stops running, a build goes nowhere. The first sign is usually a frustrated customer or a missed deadline. At that point you are already behind, and you are trying to explain something you are only just learning about yourself.
Three hours is a long time to be in the dark.
Timeline
- 14:40 UTC - Bolt.new started experiencing a bigger problem.
- Roughly 14:40 to 18:02 UTC - The disruption ran for about three hours.
- 18:02 UTC - Bolt.new resolved the issue and confirmed recovery.
How a watcher catches this before your users do
Bolt.new, like most tools, publishes a public status page. When something goes wrong, they update it. The gap for most people is that nobody is watching that page. NoCrash reads it every minute. The moment Bolt.new’s own status page flips from working to having trouble, NoCrash sends you a plain-language message telling you what is going on, in words you can act on, without you having to go check anything yourself.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those too. If you give it a URL or add a small JS snippet to your app, it watches that as well. So a quiet stall on your own side surfaces alongside anything happening upstream.
To be clear about what this is: NoCrash reads the tool’s own public report. It does not find the outage before Bolt.new knows about it. What it does is make sure you hear about it within a minute of Bolt.new’s own report, in plain English, sitting next to everything else you build on, instead of hearing about it from a customer two hours later.
The authoritative account
For the official record of this outage, go to Bolt.new’s status page directly: https://status.bolt.new/proxy/status.bolt.new