what happened
Bolt.new had a significant problem on June 12, 2026, starting at 16:10 UTC. It lasted about four hours and was resolved at 20:27 UTC. Bolt.new has since confirmed the issue is resolved. The status note gives no further detail on cause or what was affected, so neither do we.
who this hits and how they usually find out
If you build on Bolt.new, your projects, your prototypes, your client work all depend on it being available. When it stops working, nothing inside Bolt.new tells you. There is no alert, no email, no red banner that says “your work is paused.” What usually happens is this: a client tries to view something you sent them, it does not load, and they message you. Or you sit down to work and nothing responds, and you spend twenty minutes wondering if you did something wrong before you think to check whether Bolt.new itself is the problem. That gap, between the moment the tool stops working and the moment you find out, is where the damage happens.
why this is especially rough if you are not an engineer
An engineer can pull logs, check error output, run a quick test and confirm the problem is upstream. A solo operator or a non-technical founder has none of that. The work just stops moving. A workflow you set up does not fire. A build does not save. There is no error on the screen, just silence. The first real signal is often a customer asking why something is broken, at which point you are already behind. You are explaining a problem you did not know existed, to someone who noticed before you did.
timeline
- 16:10 UTC, June 12, 2026: Bolt.new began experiencing a significant problem.
- The disruption lasted approximately four hours.
- 20:27 UTC, June 12, 2026: Bolt.new recovered and confirmed the issue resolved.
how a watcher catches this before your users do
NoCrash reads Bolt.new’s public status page once every minute. The moment that page moves from working to having trouble, NoCrash sends a plain-language message explaining what is going on, in words you can act on without being technical. You do not have to remember to check the status page. You do not have to find out from a customer.
It also watches the things you ship. If you have n8n workflows, NoCrash watches them through your API token, so a quiet stall on your own side surfaces the same way. If you have an app or a page you want watched, you give NoCrash a URL or drop in a small JS snippet, and it watches that too. The combination means that whether the problem is Bolt.new’s side or yours, you hear about it in one place, in plain English, before anyone else does.
To be clear about what this is: NoCrash catches the trouble within a minute of Bolt.new’s own public report. It does not find outages before Bolt.new knows about them. It just makes sure you hear about it right away, in plain words, without having to go looking.
the official source
For the authoritative account of this outage, see Bolt.new’s own status page at https://status.bolt.new/proxy/status.bolt.new.