On the evening of July 22, 2026, Bolt.new reported a bigger problem starting at 20:51 UTC. It lasted about an hour and was marked resolved at 22:03 UTC. Bolt.new has since confirmed the disruption is over.
Who this kind of outage hits
If you build on Bolt.new, you probably were not staring at a status page at 8:51 on a Wednesday evening. Most people find out something broke when a customer writes in, or when they check in the next morning and notice nothing moved. The gap between “the tool stopped working” and “I found out” is almost always filled by a confused or frustrated user, not by an alert. That is the normal shape of this kind of thing, and it is uncomfortable.
Why it is especially rough without a technical background
When something like this happens, there is no error log to open, no red screen to screenshot, no obvious place to look. Work just stops moving. A workflow that should have run at 9 PM simply did not. An app that should have responded went quiet. The first signal is usually a customer asking why something is broken, at which point you are already behind. You are explaining an outage you did not know about, on a timeline you cannot fully account for.
What the timeline looked like
Bolt.new’s own status page flagged a bigger problem at 20:51 UTC on July 22, 2026. The disruption ran for about one hour. Bolt.new marked it resolved at 22:03 UTC the same evening.
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 check anything yourself. That turns “my customer told me at 10 PM” into “I got a calm heads-up at 8:52.” It does not find the problem before Bolt.new reports it, but it catches the report within a minute and puts it in front of you in plain English, sitting next to everything else you build on.
NoCrash also watches the things you ship. If you have n8n workflows, it watches those too. If you give it a URL or add a small JS snippet to your app, it watches that side as well. So if something goes quiet on your own end, that surfaces alongside any tool-side trouble.
For the authoritative account of this outage, see Bolt.new’s official status page: https://status.bolt.new/proxy/status.bolt.new