On July 17, 2026, Bolt.new reported a bigger problem starting at 18:20 UTC. It lasted about five minutes and was marked resolved at 18:25 UTC. Bolt.new has since confirmed the disruption is over.
Who this kind of outage hits
If you build on Bolt.new, you probably are not staring at its status page when something goes wrong. You are working on something else, or you are asleep, or you are with a customer. The first sign that anything broke is often a message from someone who tried to use what you built and found it broken. That gap, between when the tool stopped working and when you heard about it, is the part that costs you. Five minutes is short, but the shape of the problem is the same whether it lasts five minutes or five hours.
Why this is especially rough without a technical background
When a tool like Bolt.new has trouble, there is no error on your screen. Nothing in your workflow turns red. The work just stops moving and you have no way to know if the problem is on your side or theirs. A non-engineer has no logs to pull, no server to check. The only signal is silence, and silence looks exactly the same whether everything is fine or something is badly broken. So you wait, or you start second-guessing your own setup, and meanwhile a customer is already frustrated.
Timeline
- 18:20 UTC, July 17, 2026: Bolt.new reports a bigger problem.
- About 5 minutes of disruption.
- 18:25 UTC, July 17, 2026: Bolt.new marks the issue resolved.
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 looking. That turns “my customer just told me something is broken” into “I got a heads-up within a minute of Bolt.new’s own report.” For a five-minute outage like this one, that kind of speed is the difference between knowing and not knowing at all.
NoCrash also watches the things you ship. If you have n8n workflows, it watches those through your API token. If you have an app, it watches it through a URL you give it or a small JS snippet you drop in. So if the trouble is on your side rather than Bolt.new’s, that surfaces too, in the same place, in the same plain language.
To be clear about what this is: NoCrash reads what Bolt.new publicly reports. It does not find outages before Bolt.new’s own status page does. It just makes sure you hear about it right away, in plain English, without having to check anything yourself.
For the authoritative account of this outage, see Bolt.new’s official status page at https://status.bolt.new/proxy/status.bolt.new.