On the morning of July 24, 2026, Bolt.new reported a bigger problem starting at 09:15 UTC. It lasted about 22 minutes and was resolved by 09:37 UTC. Bolt.new has since confirmed the disruption is over. 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, a 22-minute disruption during working hours is enough to stall a project, break a demo, or leave a client staring at something that just stopped. The hard part is that you probably did not find out from Bolt.new. You found out because someone messaged you. A customer, a colleague, a client asking why something is not loading. That is the normal shape of this: the tool goes quiet, nothing on your screen tells you, and the first signal is someone else’s frustration landing in your inbox.
Why this is especially rough if you are not an engineer
There are no logs to read. There is no error message pointing at the cause. The work just stops moving, and you have no way to know whether the problem is on your side or theirs. So you start checking things you did not break, reloading pages, wondering if you changed something. By the time you figure out it is a platform-wide problem, you have already lost time and possibly already have an unhappy person waiting on you. That gap, between when the tool stops working and when you know it stopped working, is where the damage happens.
Timeline
- 09:15 UTC - Bolt.new reports a bigger problem begins.
- 09:37 UTC - Bolt.new reports the disruption is resolved.
- Total duration - about 22 minutes.
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 telling you what it saw, in words you can act on immediately. You do not have to check the status page yourself, and you do not have to wait for a customer to tell you something is wrong.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those through your API token. If you have an app or a page, you can give NoCrash 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 alongside anything happening at the platform level.
To be clear about what this is: NoCrash reads the tool’s own public status page. It does not find the outage before the tool reports it. What it does is make sure you hear about it in plain English, within a minute of the tool’s own report, without having to go looking.
For the authoritative account of this disruption, see the official Bolt.new status page: https://status.bolt.new/proxy/status.bolt.new