On July 20, 2026, Bolt.new had a significant disruption starting at 13:25 UTC. It lasted roughly two hours and was resolved by 16:10 UTC. Bolt.new has since confirmed the issue is resolved. No detailed cause has been published at the time of writing.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, your work lives inside it. When it goes quiet, your projects stall, your automations stop, and nothing inside the tool tells you why. Most operators find out the same way: a customer writes in asking why something is broken, or a client notices a deliverable is late. By that point the outage may already be over, but the damage to trust is done. The gap between “the tool stopped working” and “I found out” is where the real cost lives.
Why this is especially rough without a technical background
A developer can pull up logs, check error messages, and at least confirm the problem is not on their side. If you are running a business on top of a tool and you are not an engineer, none of that is available to you. The work just stops moving. No red screen, no alert, no explanation. The first signal is often an unhappy customer or a missed deadline, and by then you are already behind. You spend time second-guessing yourself, wondering if you broke something, before you even think to check whether the tool itself is the problem.
Timeline
- 13:25 UTC, July 20, 2026 – Bolt.new begins experiencing a bigger problem.
- Roughly two hours – The disruption continues with no recovery.
- 16:10 UTC, July 20, 2026 – Bolt.new recovers and confirms the issue is resolved.
How a watcher catches this before your users do
Bolt.new, like most tools, publishes a public status page. The moment that page flips from working to having trouble, NoCrash picks it up, usually within a minute of Bolt.new’s own report, and sends you a plain-language message. Not a raw status code. Not a wall of technical text. Just: “Bolt.new is reporting a bigger problem right now.” That lands in one place alongside everything else you build on, so you are not checking five different status pages manually.
NoCrash also watches the things you ship. If you have n8n workflows running, it watches those too. If you give it a URL or add a small JS snippet to your app, it watches that as well. So if something goes quiet on your own side, that surfaces alongside any tool-level trouble. The result is that “my customer told me” becomes “I got a calm heads-up first,” with enough time to post a quick note to clients before anyone asks.
To be clear about what this is: NoCrash reads public status pages and watches the specific things you point it at. It does not find outages before the tool’s own status page does.
For the authoritative account of this outage, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.