Bolt.new had a significant disruption starting at 23:06 UTC on July 16, 2026. It lasted about 57 minutes and was resolved by 00:03 UTC on July 17. Bolt.new has since reported the issue as resolved.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, a disruption like this lands quietly. You are not sitting at your screen at 11 pm watching a progress bar. Your project is just there, or it isn’t. The people who notice first are often the ones you least want hearing about it: a client who tries to open something you built, a collaborator who hits a wall, or a customer who sends a message that starts with “hey, is this broken?” That gap between when the tool stopped working and when you found out is where the damage happens. Not the outage itself, but the silence around it.
Why this is especially rough if you are not an engineer
There is no error log to open. There is no red light on a screen you are watching. The work just stops moving, and nothing tells you why. If you have an n8n workflow that hands off to something built on Bolt.new, the run does not fail loudly. It stalls, or queues up, or produces nothing, and you find out when someone downstream asks where their thing is. A non-engineer operator has no obvious place to look. The first signal is almost always a frustrated person on the other end of a message.
What the timeline looked like
Bolt.new started showing a bigger problem at 23:06 UTC on July 16, 2026. The disruption lasted about 57 minutes. It was resolved at 00:03 UTC on July 17, 2026.
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 status code, not a raw alert. A sentence you can read and act on, sitting next to everything else you build on. For a 57-minute disruption like this one, that means you could have known within a minute of Bolt.new’s own report, instead of finding out from a customer.
NoCrash also watches the things you ship. If you have n8n workflows, it watches those. If you have an app or a page, you can give it a URL or drop in a small JS snippet and it will watch that too. So if something goes quiet on your own side, that surfaces as well. It does not replace Bolt.new’s own status page. It reads that page and tells you what it says, in plain English, in one place.
For the authoritative account of this outage, see Bolt.new’s official status page at https://status.bolt.new/proxy/status.bolt.new.