On July 21, 2026, Bolt.new reported a bigger problem starting at 10:15 UTC. It lasted about 56 minutes and was resolved at 11:12 UTC. Bolt.new has since confirmed the disruption is over.
Who this kind of outage hits
If you build on Bolt.new, you probably found out about this the hard way. A customer tried something, it did not work, and they messaged you. Or a workflow you rely on quietly stopped producing results and you only noticed when something downstream went missing. That is the normal shape of this. The tool does not tap you on the shoulder. You find out from someone who is already frustrated.
Most people who build on hosted tools have no automatic way to know when the tool itself is having trouble. They check their own code, their own settings, their own recent changes. They spend time looking in the wrong place. Meanwhile the problem is upstream, and the tool’s own status page already says so.
Why this is especially rough without a technical background
When you are not an engineer, there is no log file to open. There is no error message pointing at the real cause. The work just stops moving. A form does not submit. A build does not finish. An automation runs but produces nothing. The silence is the only signal, and silence is easy to misread as your own mistake. By the time you have ruled out everything on your side, your customer has already sent the message.
That gap, between when the tool started having trouble and when you found out, is where the damage happens.
Timeline
- 10:15 UTC, July 21, 2026: Bolt.new reports a bigger problem begins.
- About 56 minutes of disruption.
- 11:12 UTC, July 21, 2026: Bolt.new reports the problem is resolved.
How a watcher catches this before your users do
NoCrash reads Bolt.new’s public status page once a minute. The moment that page flips from working to having trouble, NoCrash sends you a plain-language message. Not a raw status code. Not a technical alert. A sentence you can read and act on, sitting next to everything else you build on.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those through your API token. If you have an app, you can give it a URL or drop in a small JS snippet, and NoCrash watches that too. So if something goes quiet on your side, that surfaces as well.
The honest limit: NoCrash reads the tool’s own public status page. It does not find the problem before the tool reports it. What it does is catch that report within a minute and tell you in plain English, so you hear it before your customers do, not after.
The official source
For the authoritative account of this outage, see Bolt.new’s own status page: https://status.bolt.new/proxy/status.bolt.new