On July 15, 2026, Bolt.new experienced a significant disruption starting at 14:20 UTC. It lasted about 42 minutes and was resolved by 15:03 UTC. Bolt.new has since reported the issue as resolved.
Who this kind of outage hits
If you build on Bolt.new, your projects, your app previews, and anything you are actively shipping through it all depend on it being up. When it goes quiet, you usually do not get a notification. You find out because a client emails asking why their new feature is not there, or a customer tries something you promised them and it does not work. That gap between “the tool stopped” and “I found out” is where the damage happens. Most operators discover it the wrong way.
Why it is especially rough without a technical background
There is no error log to open. There is no red screen telling you something broke. The work just stops moving and everything looks normal until it does not. If you are running automations or builds through Bolt.new, they may have stalled silently during those 42 minutes with no signal on your end. The first sign is often a confused or frustrated customer, and by then you are already behind. You are explaining something you did not know about yet.
What the timeline looked like
- 14:20 UTC - Bolt.new started experiencing a bigger problem.
- 14:20 to 15:03 UTC - The disruption continued for about 42 minutes.
- 15:03 UTC - Bolt.new reported the issue 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, within a minute of Bolt.new’s own report, and sends you a plain-language message. Not a raw status code. A sentence you can read and act on immediately. That turns “my customer told me two hours later” into “I got a heads-up at 14:21 and knew what was happening.”
NoCrash also watches the things you ship. If you have n8n workflows running, it watches those too. If you give it a URL or drop in a small JS snippet, it watches your app directly. So if something goes quiet on your side, that surfaces as well. It does not replace Bolt.new’s own status page, and it does not claim to find problems before Bolt.new reports them. It just makes sure you are not the last to know when they do.
For the authoritative account of this outage, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.