On the morning of July 22, 2026, Bolt.new reported a bigger problem starting at 08:40 UTC. It lasted about 7 minutes and was resolved by 08:47 UTC. Bolt.new has since confirmed the disruption is over.
Who this kind of outage hits
If you build or ship something on Bolt.new, a short outage like this usually lands on you in the worst possible way: a customer messages you asking why something is broken. Not an alert, not a warning. A customer. By the time that message arrives, the disruption may already be over, but the damage to trust is done. Seven minutes is short, but if a customer hit a wall during those seven minutes and you had no idea, that is still a conversation you have to have after the fact.
Why it is especially rough without a technical background
When a tool you rely on goes quiet, there is nothing on your screen that explains it. No error message you can act on, no log to read. The work just stops. A form does not submit, a build does not finish, a workflow stalls. If you are not an engineer, you have no obvious place to look. You might spend time wondering whether you did something wrong. The first clear signal is often an unhappy user, and by then you are already behind.
What the timeline looked like
- 08:40 UTC - Bolt.new reported a bigger problem.
- 08:47 UTC - Bolt.new confirmed the disruption was resolved.
- Total duration - about 7 minutes.
The cause has not been detailed in Bolt.new’s public status note. See the official source below for any updates.
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, sitting next to everything else you build on. You find out within a minute of Bolt.new’s own report, not from a customer.
That same watcher also keeps an eye on the things you ship. If you have n8n workflows, NoCrash watches those too. If you have an app, you can give it a URL or drop in a small JS snippet and it will watch that as well. So a quiet stall on your own side surfaces alongside any trouble on the tools underneath it.
To be clear about what this is: NoCrash reads what Bolt.new publishes. It does not find the outage before Bolt.new’s own status page does. But it means you are reading that page constantly, automatically, and in plain English, instead of finding out from a user.
For the authoritative account of this outage, see Bolt.new’s official status page: https://status.bolt.new/proxy/status.bolt.new