On July 17, 2026, Bolt.new reported a bigger problem starting at 15:05 UTC. It lasted about 24 minutes and was marked resolved at 15:30 UTC. Bolt.new has since confirmed the disruption is over.
Who this kind of outage hits
If you build or ship something on Bolt.new, a 24-minute gap in the middle of the day can quietly swallow work. The hard part is that nothing inside the tool usually tells you. No alert, no red banner, no email. You find out because a customer tries something, it fails, and they write to you. By then the outage is already over, but the damage to trust is fresh. That “my customer told me before I knew” shape is the normal experience for solo operators and small teams who are not watching a tool’s status page by hand.
Why this is rough without a technical background
When you are not an engineer, there is no log to open and no error to read. The work just stops moving. A build stalls, a project does not save, a workflow produces nothing. The first signal is silence, and silence looks the same whether the problem is on your side or theirs. So you spend time checking your own setup, restarting things, wondering if you broke something, before you even think to check whether the tool itself is having trouble. That delay costs you time and composure, and it costs your customers confidence.
Timeline
- 15:05 UTC - Bolt.new reports a bigger problem begins.
- 15:30 UTC - Bolt.new marks the disruption resolved.
- Total duration - about 24 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 check anything yourself. That turns “my customer told me an hour later” into “I got a calm heads-up within a minute of Bolt.new’s own report.” It sits next to everything else you build on, so you are not juggling a dozen status pages.
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 something goes quiet on your own side, that surfaces too, separately from what the tool reports.
To be clear about what it does not do: NoCrash reads what the tool’s own status page says. It does not find trouble before the tool reports it. It just makes sure you hear about it right away, in plain English, in one place.
For the authoritative account of this outage, see Bolt.new’s own status page: https://status.bolt.new/proxy/status.bolt.new