What actually caused this?

Bolt.new has not published a detailed cause, at least not in what is publicly available right now. The official status page at https://status.bolt.new/proxy/status.bolt.new is the right place to check if they add more detail.

Could this happen again?

Yes. Any tool can have another outage. Bolt.new is not unusual in that, and this is not a reason to stop using it. It is a reason to have something watching it so you are not the last to know.

How do I find out faster next time something like this breaks?

NoCrash reads Bolt.new's public status page every minute. The moment Bolt.new reports a problem, NoCrash translates it into plain English and tells you. You do not have to check anything. You hear about it within a minute of Bolt.new's own report, not hours later from a frustrated customer.

Bolt.new outage: about 4 days of bigger problems, July 10-15 2026

Bolt.new had a bigger problem starting July 10, 2026 at 21:53 UTC. It lasted about four days, recovering on July 15 at 07:39 UTC. Bolt.new has since marked it resolved. That is the full picture the official source gives us, and we will not dress it up with details that were not published.

Who this kind of outage hits, and how they usually find out

If you build on Bolt.new, you are probably not watching its status page. You are building, shipping, talking to customers. The first sign something is wrong is usually a customer message: “hey, this isn’t working.” By then the disruption has been running for hours, maybe longer. You have no idea when it started, whether it is your code or the tool, or what to tell the customer. That gap, between when the tool stopped working and when you found out, is where trust quietly drains away.

Why this is especially rough if you are not an engineer

There is no error on your screen. Nothing crashes loudly. The work just stops moving. A form does not submit. A build does not finish. An automation sits there. You refresh, you wait, you wonder if you did something wrong. Without someone watching the tool’s own status page, there is no way to know it is a platform problem and not yours. The first real signal is an unhappy customer, and by then you are already behind.

Timeline

Started: July 10, 2026 at 21:53 UTC
Recovered: July 15, 2026 at 07:39 UTC
Duration: about 4 days
Current status: resolved, per Bolt.new’s official page

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. Not a raw status code. Not a link you have to decode. A sentence that tells you what is wrong, in words you can 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 too. If you give it a URL or drop in a small JS snippet, it watches your app. So if something goes quiet on your own side, that surfaces as well.

To be straight with you: NoCrash reads the tool’s own public status page. It does not find the outage before Bolt.new reports it. What it does is make sure you hear about it within a minute of Bolt.new’s own report, in plain English, without you having to check anything yourself. That turns “my customer told me four days in” into “I got a calm heads-up the same evening it started.”

The authoritative account

For the official record on this outage, go to https://status.bolt.new/proxy/status.bolt.new. That page is the source of truth.