what happened
Bolt.new reported a bigger problem on June 13, 2026, starting at 02:10 UTC. It lasted about two minutes before recovering at 02:13 UTC. Bolt.new has since marked it resolved.
who this kind of outage hits, and how they usually find out
If you build or ship something on Bolt.new, a short disruption like this can pass completely silently on your end. No alert fires. No error lands in your inbox. The work just stops for a couple of minutes, and if something queued up or a user hit the tool at exactly the wrong moment, the first you hear about it is a message from them. That is the normal shape of this: a customer notices before you do, and you spend the next twenty minutes trying to figure out whether the problem was yours or theirs.
why this is especially rough without a technical background
A developer can pull logs, check error traces, and piece together a timeline after the fact. If you are running a business on top of a tool like Bolt.new without that background, none of those options exist. There is no screen that says “this was Bolt.new, not you.” The work just goes quiet. You start second-guessing your own setup, your own workflows, your own recent changes. By the time you find the status page, the outage may already be over and you still have no clean answer to give the customer who asked.
timeline
- 02:10 UTC, June 13, 2026: Bolt.new reports a bigger problem.
- 02:13 UTC, June 13, 2026: Bolt.new marks the disruption resolved.
- Total duration: about 2 minutes.
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 a plain-language heads-up, in words you can act on, without you having to go looking. For a two-minute disruption like this one, that means the gap between “something is wrong” and “you know about it” shrinks to roughly the time it takes to read one short message.
That same watcher sits next to everything else you build on. If you have n8n workflows running, NoCrash watches those too. If you have an app or a page you want watched, you can give it a URL or drop in a small JS snippet and it will surface a quiet stall on your own side as well. The point is not to replace the tool’s own status page. NoCrash does not find problems before the tool reports them, and it does not make its own judgment calls about whether a tool is healthy. It reads what the tool says publicly, as fast as it says it, and puts it in front of you in plain English before a customer gets there first.
the authoritative account
For the official record of this disruption, see the Bolt.new status page directly: https://status.bolt.new/proxy/status.bolt.new