On July 17, 2026, Bolt.new experienced a significant disruption starting at 18:30 UTC. It lasted roughly one hour and was resolved by 20:22 UTC. Bolt.new has since reported the issue as resolved.
Who this kind of outage hits
If you build or ship something on Bolt.new, a disruption like this usually reaches you the wrong way. Not through an alert you set up. Through a customer message, a confused reply to an email, or a support ticket that arrives hours after the fact. By then the damage is already done, and you are explaining something you did not know was happening. That gap, between when the tool stopped working and when you found out, is the part that costs you.
Why it is especially rough without a technical background
When something like this happens, there is no error screen waiting for you. No log file to open. The work just stops moving and nothing tells you why. If you are running automations, they go quiet. If you are building something live, it simply does not respond the way it should. The first real signal is often an unhappy person on the other end. That is a hard position to be in, because you cannot fix what you do not know is broken, and you cannot communicate clearly with customers when you are finding out at the same time they are.
Timeline
- 18:30 UTC, July 17, 2026: Bolt.new begins experiencing a bigger problem.
- About 1 hour: The disruption continues with no recovery.
- 20:22 UTC, July 17, 2026: Bolt.new reports the issue resolved.
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 looking. That does not mean NoCrash finds the problem before Bolt.new does. It means you hear about it within a minute of Bolt.new’s own report, instead of hearing about it from a customer an hour later.
NoCrash also watches the things you ship. If you have n8n workflows, it watches those. If you have an app, you can give it a URL or drop in a small JS snippet, and it watches that too. So if something goes quiet on your own side, that surfaces alongside everything else in one place, in plain English.
The combination is simple: you stop being the last to know.
For the authoritative account of this outage, see Bolt.new’s official status page at https://status.bolt.new/proxy/status.bolt.new.