What happened
Bolt.new reported a bigger problem on June 30, 2026, starting at 14:35 UTC. It lasted about 11 minutes and was marked resolved at 14:47 UTC. The tool has since confirmed the disruption is over.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, a short disruption like this can still cause real damage, because you probably did not know it was happening in real time. The usual way people find out is a customer message: something did not load, a build did not finish, a link they shared stopped working. By the time that message arrives, the outage may already be over, but the customer’s trust is already shaken. There is no alert inside Bolt.new that says “we are having trouble right now, hold off.” You are just left guessing.
Why this is especially rough if you are not an engineer
When a tool goes quiet, there is nothing to read. No error on your screen, no log file, no red light. The work just stops moving. You might refresh a few times, wonder if it is your connection, and move on, not realizing anything broke. The first real signal is often an unhappy customer asking why something is not working. At that point you are already behind, explaining a problem you did not know existed, with no information to give them.
Timeline
- 14:35 UTC, June 30, 2026 - Bolt.new’s status page showed a bigger problem.
- About 11 minutes of disruption - the tool was affected during this window.
- 14:47 UTC, June 30, 2026 - Bolt.new marked the disruption resolved.
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, in words you can act on, without you having to go check anything yourself. For an 11-minute disruption like this one, that means you hear about it within a minute of Bolt.new’s own report, not from a frustrated customer an hour later.
NoCrash also watches the things you ship: your n8n workflows through an API token, and your app through a URL you give it or a small JS snippet you drop in. So if something goes quiet on your own side, that surfaces too, sitting next to everything else you build on.
To be straight about what this is: NoCrash reads what Bolt.new publishes. It does not find the problem before Bolt.new does. What it does is make sure you are not the last to know.
The official source
For the authoritative account of this disruption, see Bolt.new’s own status page at https://status.bolt.new/proxy/status.bolt.new.