On the morning of July 16, 2026, Bolt.new reported a bigger problem starting at 08:45 UTC. It lasted about 10 minutes and was resolved by 08:55 UTC. Bolt.new has since confirmed the disruption is over.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, a short outage like this probably did not send you any alert. You were likely working on something else. The first sign something was wrong may have come from a user asking why their project would not load, or from you checking in and noticing things felt off. That is the usual shape of it: the tool goes quiet, nothing on your screen explains why, and the first real signal is a confused or frustrated person on the other end.
Ten minutes is short. But if a customer hit Bolt.new during that window and got nothing, they did not know it was a platform issue. They just knew it did not work.
Why this is especially rough without a heads-up
When you are not an engineer, there is no log to pull, no error trace to read. The work just stops. You cannot tell whether it is your project, your browser, your internet, or the platform itself. So you start checking things one by one, losing time, while the real answer is sitting on a status page you did not know to look at. By the time you find it, the disruption may already be over, but the customer has already sent the message.
What the timeline looked like
- 08:45 UTC - Bolt.new reported a bigger problem
- 08:55 UTC - Bolt.new confirmed the disruption was resolved
- Total duration - about 10 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 explaining what is going on, in words you can act on, without you having to go find it yourself. That turns “my user just told me something is broken” into “I already knew, ten minutes ago, in plain English.”
It also watches the things you ship. If you have n8n workflows running, NoCrash watches those too. And if you give it a URL or add a small JS snippet to your app, it watches that as well. So a quiet stall on your own side surfaces the same way, in the same place.
NoCrash does not find outages before Bolt.new’s own status page does. It reads that page and tells you within a minute of Bolt.new’s own report. That is the honest version of what it does, and for most operators, that alone closes the gap.
For the authoritative account of this disruption, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.