On July 21, 2026, Bolt.new reported a bigger problem starting at 14:04 UTC. It lasted about three hours and was resolved at 17:08 UTC. Bolt.new has since confirmed the disruption is over.
Who this hits and how they usually find out
If you build on Bolt.new, your projects, your automations, or your customers’ experience can go quiet without any alarm going off on your side. The tool stops working, but nothing tells you directly. Most operators find out the same way: a customer writes in asking why something is broken, or they notice it themselves hours later while checking in. By then the damage is already done, the customer is already annoyed, and you are already behind.
Why this is especially rough without a technical background
When something like this happens, there are no logs to read and no error message on your screen. The work just stops moving. A build stalls, a workflow sits idle, an app stops responding to users. The first signal is often an unhappy message from someone who paid you. That gap, between when the tool went quiet and when you found out, is the part that costs you the most. Not just time, but trust.
Timeline
- 14:04 UTC, July 21, 2026 - Bolt.new reported a bigger problem beginning.
- About 3 hours - the disruption continued with no resolution.
- 17:08 UTC, July 21, 2026 - Bolt.new confirmed the issue was resolved.
How a watcher catches this before your users do
NoCrash reads Bolt.new’s own public status page once every minute. The moment that page flips from working to having trouble, NoCrash sends you a plain-language message explaining what is wrong, in words you can actually act on. You do not have to check the status page yourself, translate technical language, or wait for a customer to tell you something is broken.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those through your API token. If you have an app, you can give NoCrash a URL or drop in a small JS snippet and it will watch that too. So if the problem is on your side rather than Bolt.new’s side, that surfaces as well.
To be clear about what this means: NoCrash catches the outage within a minute of Bolt.new’s own public report. It does not find the problem before Bolt.new does. But it means you hear about it in plain English, in one place, right away, instead of from a frustrated customer.
For the authoritative account of this outage, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.