On the morning of July 17, 2026, Bolt.new reported a bigger problem starting at 06:55 UTC. It lasted about 10 minutes and was marked resolved at 07:05 UTC. Bolt.new has 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 disruption like this can still cause real trouble. A project that was mid-build stalls. A workflow that hands off to Bolt.new quietly stops. And the first signal most people get is not an alert. It is a customer asking why something is broken, or a teammate saying the thing they needed is not there. Ten minutes feels short until you are the one explaining it.
Why it is especially rough if you are not an engineer
There is no error on your screen. Nothing says “Bolt.new is having trouble.” The work just stops moving, and you have no way to know whether the problem is on your side or theirs. You start checking your own setup, retracing your steps, wondering what you changed. By the time you find the status page, the outage may already be over, but the confusion and the customer message are still sitting in your inbox.
What the timeline looked like
- 06:55 UTC - Bolt.new reported a bigger problem.
- 07:05 UTC - Bolt.new marked the disruption 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, in words you can act on, without you having to go find the status page yourself. That turns “my customer told me something is broken” into “I got a heads-up within a minute of Bolt.new’s own report.”
It also watches the things you ship. If you have n8n workflows, NoCrash watches those too. If you give it a URL or add a small JS snippet to your app, it watches that as well. So if the trouble is on your own side rather than Bolt.new’s, that surfaces in the same place. Everything you build on and everything you ship, one calm message when something goes wrong.
For the authoritative account of this disruption, see Bolt.new’s official status page at https://status.bolt.new/proxy/status.bolt.new.