On July 17, 2026, Bolt.new had a significant problem starting at 07:15 UTC. It lasted about five hours and was resolved at 12:22 UTC. Bolt.new has since reported it as resolved.
Who this kind of outage hits
If you build on Bolt.new, you are probably not watching its status page while you work. Most people are not. So when something like this happens in the early morning, the first sign is often a customer writing in to say something is broken, or a collaborator asking why a project link stopped loading. By the time that message arrives, the disruption has already been running for an hour or two. You are now explaining a problem you did not know about, to someone who noticed before you did.
That gap, between when the tool stopped working and when you found out, is the rough part. Not the outage itself.
Why this is especially hard without an engineering team
If you have engineers, someone is probably watching logs. If you are a solo founder or a small team running automations, there are no logs to read. Nothing on your screen says “Bolt.new is having trouble.” Your work just quietly stops moving. A build does not finish. A workflow does not trigger. A link does not load. The silence looks like your own mistake at first, so you spend time checking your own setup before you even think to check whether the tool itself is the problem. By then, a customer has already noticed.
Timeline
- 07:15 UTC, July 17, 2026 – Bolt.new began experiencing a bigger problem.
- About 5 hours – the disruption ran without a full resolution.
- 12:22 UTC, July 17, 2026 – Bolt.new reported the issue resolved.
How a watcher catches this before your users do
NoCrash reads Bolt.new’s public status page once 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 check anything yourself. That means instead of hearing about it from a customer, you hear about it within a minute of Bolt.new’s own report, and you can get ahead of it.
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 a quiet stall on your own side surfaces the same way, in the same place.
To be clear about what it does not do: NoCrash does not find the outage before Bolt.new’s own status page does. It reads that page and tells you quickly, in plain English, so you are not the last to know.
For the authoritative account of this outage, see Bolt.new’s official status page at https://status.bolt.new/proxy/status.bolt.new.