On July 20, 2026, Bolt.new reported a bigger problem starting at 16:11 UTC. It lasted about two hours and was resolved at 18:38 UTC. Bolt.new has since confirmed the disruption is over.
Who this kind of outage hits
If you build or run something on Bolt.new, a two-hour window where the tool is struggling is two hours where your work stops moving and you probably have no idea. Most people find out the wrong way: a customer messages them, a client asks why something is broken, or they stumble on it themselves while checking in on something else. The tool does not call you. Nothing inside it waves a flag. You are just quietly in the dark until someone outside your team notices first.
Why it is especially rough without a technical background
When a developer hits a problem, they can pull up logs, check error messages, and at least know something is wrong. When you are a non-engineer operator, there is nothing to read. The work just stops. A workflow does not run, an app does not respond, a build does not finish. The first signal is often an unhappy customer, and by then you are already behind. You are explaining a problem you did not know existed, to someone who noticed before you did.
What the timeline looked like
- 16:11 UTC - Bolt.new reported a bigger problem starting.
- ~18:38 UTC - Bolt.new confirmed the issue was resolved.
- Total duration - about 2 hours and 27 minutes.
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. That turns “my customer just told me something is broken” into “I got a heads-up within a minute of Bolt.new’s own report.” It sits next to everything else you build on, so you are not checking five different status pages yourself.
NoCrash also watches the things you ship. If you have n8n workflows, it watches those. If you have an app, it watches it 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, separately from what the tool itself is reporting.
To be clear about what it does not do: NoCrash does not find the outage before Bolt.new’s own status page does. It reads that page and tells you fast, in plain English, in one place.
For the authoritative account of this outage, see Bolt.new’s official status page at https://status.bolt.new/proxy/status.bolt.new.