what happened
Bolt.new had a significant outage starting June 14, 2026 at 18:40 UTC. It lasted about 8 hours and was resolved by 03:38 UTC on June 15. Bolt.new’s own status page described it as a bigger problem. The disruption is now over.
who this hits and how they usually find out
If you build on Bolt.new, your projects, your prototypes, and anything you are actively shipping through it all depend on it being available. When it goes quiet, nothing inside the tool tells you. There is no alarm, no email, no red banner. You find out because a client tries to access something you built and it does not load, or because you sit down to work and nothing responds. The worst version is a customer writing in to say something is broken, and you are the last person to know. That gap, between the moment the tool stopped and the moment someone complained, is where the damage happens.
why this is especially rough without a technical background
A developer can pull up logs, check error traces, and at least confirm the problem is not on their end. A solo founder or automation operator has none of that. The work just stops moving. A form stops submitting, a workflow goes quiet, a client-facing app shows nothing useful. There is no error on your screen telling you why. You start second-guessing yourself: did I break something? Did a payment lapse? Is it my internet? By the time you have ruled all that out and landed on “the tool itself is down,” you have already lost time, and your customer has already lost patience.
timeline
- June 14, 2026 at 18:40 UTC, Bolt.new’s status page reported a bigger problem.
- The disruption ran for about 8 hours.
- June 15, 2026 at 03:38 UTC, Bolt.new reported the issue 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 a plain-language message, in words that do not require a technical background to act on. That happens within a minute of Bolt.new’s own public report, not hours later when a customer writes in.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those through your API token. If you have an app or a page, you can give NoCrash a URL or drop in a small JS snippet and it will watch that too. So if something goes quiet on your own side, that surfaces alongside anything happening at the tool level.
None of this finds the problem before Bolt.new knows about it themselves. It just means you hear about it in plain English, in one place, at roughly the same moment the status page changes, instead of hearing about it from an unhappy customer eight hours later.
the authoritative account
For the official record of this outage, see Bolt.new’s status page directly: https://status.bolt.new/proxy/status.bolt.new