What actually caused this?

Bolt.new has not published a detailed cause at the time of writing. Their status page noted a bigger problem that has since been resolved. Check https://status.bolt.new/proxy/status.bolt.new for any updates they add.

Can this happen again?

Yes. Any tool can have another outage. Bolt.new is not unusual in that respect. The question is not whether it will happen again but whether you will find out fast enough to get ahead of it.

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

NoCrash reads Bolt.new's public status page every minute and tells you in plain language within a minute of Bolt.new's own report. You do not have to check anything. You just get a calm message that something is wrong, before a customer beats it to you.

Is there anything I should do right now?

If you had workflows or builds running on Bolt.new between 09:25 and 10:35 UTC on July 26, it is worth checking whether any of them completed as expected. Anything that ran during that window may need a manual check.

Bolt.new outage on July 26, 2026: what happened and what to do next

What happened

Bolt.new had a significant disruption on July 26, 2026. It started at 09:25 UTC and was resolved at 10:35 UTC, lasting about one hour. Bolt.new has since reported the issue resolved. No detailed cause has been published at the time of writing.

Who this hits and how they usually find out

If you build on Bolt.new, an hour of it not working properly means your app, your automations, or your builds were stalled or broken for that window. Most people find out the wrong way: a customer sends a message, a client asks why something is not working, and only then do you go looking. The tool itself rarely sends you a personal alert. You are just expected to be watching, and most of the time nobody is.

Why this is especially rough if you are not an engineer

There is no error on your screen. Nothing in your workflow says “I stopped.” The work just quietly stops moving, and you have no way to know until the silence becomes a complaint. An engineer might have logs to check. A solo operator or a small team usually has nothing except the growing feeling that something is off. By the time a customer confirms it, the disruption is already over and the damage is already done.

Timeline

09:25 UTC - Bolt.new’s public status page reported a bigger problem.
~10:35 UTC - Bolt.new reported the issue resolved.
Total duration - about 1 hour.

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 yourself. That turns “my customer just told me” into “I got a heads-up an hour ago and already knew.” It also watches the specific things you ship: your n8n workflows through an API token, and your app through a URL you give it or a small JS snippet you drop in. So if your own side goes quiet separately from Bolt.new, that surfaces too. To be clear about what it does not do: NoCrash reads the tool’s own public status page, so it catches the trouble within a minute of the tool’s own report, not before it. It is not magic. It is just faster and calmer than waiting for a customer to tell you.

The authoritative account

For the official record of this outage, go to Bolt.new’s own status page: https://status.bolt.new/proxy/status.bolt.new