What happened
Bolt.new had a bigger problem starting just before 1 a.m. UTC on June 13, 2026. It lasted about 27 minutes, recovering at 01:23 UTC. Bolt.new has since reported the issue resolved. What caused it, exactly, is not something they have detailed publicly, so this postmortem will not guess.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, you are probably using it to spin up apps, prototype features, or ship something a client or customer is waiting on. When the tool goes quiet, nothing inside it waves a flag at you. No alert, no message, no red banner. You find out the way most people find out: a customer tries something, it does not work, and they send you a message. By the time that message arrives, the outage may already be over, but the damage to trust is done. You are now explaining a problem you did not know existed, to someone who noticed before you did.
Why this is especially rough without a technical background
If you are not an engineer, there is no log to open, no error trace to read. The work just stops moving and the screen looks completely normal. A build stalls, a workflow sits idle, an app does not load for someone. You have no way to know whether the problem is on your end or theirs. So you start checking things you can check: your internet connection, your browser, whether you saved correctly. Meanwhile the real cause is sitting on a status page you did not know to look at. That gap, between something going wrong and you understanding why, is where the stress lives.
Timeline
- 00:55 UTC, June 13, 2026: Bolt.new begins experiencing a bigger problem.
- 01:23 UTC, June 13, 2026: Bolt.new recovers. Total disruption: about 27 minutes.
How a watcher catches this before your users do
Bolt.new publishes a public status page. The moment that page flips from working to having trouble, a tool watching it every minute can send you a plain-language heads-up right away. Not an hour later. Not after a customer writes in. Within a minute of Bolt.new’s own public report.
That is what NoCrash does. It reads Bolt.new’s status page every minute. The moment something changes, it tells you in plain English, in one place, alongside everything else you build on. It 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 your own side goes quiet separately, that surfaces too.
This does not mean NoCrash finds the problem before Bolt.new knows about it. It does not. It catches the trouble within a minute of Bolt.new’s own public report, which is still well ahead of a customer complaint. The difference between “my customer told me” and “I got a calm heads-up first” is usually just whether anyone was watching that status page at all.
The authoritative account
For the official record of this outage, see Bolt.new’s own status page: https://status.bolt.new/proxy/status.bolt.new