What actually caused this?

Bolt.new has not published a detailed cause for this outage. The only confirmed information is that a bigger problem started at 09:30 UTC and was resolved by 13:13 UTC. For any updates, check the official status page linked above.

Could this happen again?

Yes, honestly. Any tool can have another outage. Bolt.new is not unusual in that. The question is not whether it will happen again but how quickly you find out when it does.

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

NoCrash reads Bolt.new's public status page every minute and sends you a plain-language heads-up within a minute of Bolt.new's own report. You do not have to go looking. It sits next to everything else you build on, so one place covers it all.

Was my own app or workflow affected separately?

This postmortem covers what Bolt.new reported on its own status page. Whether your specific workflows or app were affected depends on what you were running at the time. NoCrash watches your n8n workflows and your app directly, through a URL or a small JS snippet, so a quiet stall on your own side would surface there even if the tool's status page does not mention it.

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

On July 28, 2026, Bolt.new had a significant problem starting at 09:30 UTC. It lasted roughly three hours before recovering at 13:13 UTC. Bolt.new has since reported the issue resolved. The cause has not been published in detail.

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 while you work. Most people find out something is wrong when a customer writes in, or when they sit down to work and notice a project that should have moved has not. That gap, between when the tool stopped working and when you realized it, is almost always longer than it should be. An hour, sometimes most of a day. The tool does not send you an email. Nothing inside your workflow throws an error you can see. You just find out late.

Why this is especially rough without a technical background

When a tool like Bolt.new goes quiet, there is no log file to open, no red error on the screen. The work simply stops moving. If you are running automations or building something for a client, the first signal is often an unhappy message from someone who expected a result. By then you are already behind, already explaining, already trying to figure out whether the problem is on your side or theirs. That uncertainty is the worst part. You cannot fix what you cannot see.

What the timeline looked like

09:30 UTC - Bolt.new started having a bigger problem.
Roughly three hours - the disruption continued with no recovery.
13:13 UTC - Bolt.new recovered and later reported the issue resolved.

How a watcher catches this before your users do

NoCrash reads Bolt.new’s own public status page once 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 is not the same as finding the problem before Bolt.new does. It means you hear about it within a minute of Bolt.new’s own report, instead of whenever a customer happens to tell you.

NoCrash also watches the things you ship. If you have n8n workflows, it watches those too. If you have an app, you can give it a URL or drop in a small JS snippet and it will watch that as well. So if something goes quiet on your own side, that surfaces in the same place. One message, plain English, before your users notice.

The official account

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