On June 30, 2026, Bolt.new reported a bigger problem starting at 11:05 UTC. It lasted roughly one hour and was marked resolved at 12:55 UTC. Bolt.new has since confirmed the disruption is over. The cause has not been published in detail.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, you probably were not staring at a status page at 11:05 on a Tuesday. You were doing something else. The first sign something was wrong was likely a customer message, a missed delivery, or a workflow that quietly stopped producing results. That gap, between when the tool broke and when you heard about it, is where the damage happens. A paying customer noticed before you did, and now you are explaining something you did not know about.
Why this is especially rough if you are not an engineer
There is no error on your screen. Nothing crashes visibly. The work just stops moving. If you run automations on Bolt.new, your runs may have queued up or failed silently while you were focused elsewhere. Without logs to read or alerts to check, the only signal is an unhappy person on the other end. By the time you piece together what happened, the disruption is already over and the awkward conversation has already started.
Timeline
- 11:05 UTC - Bolt.new’s status page flagged a bigger problem.
- About one hour - the disruption ran while anything depending on Bolt.new was affected.
- 12:55 UTC - Bolt.new marked 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 check anything. That turns “my customer told me at 1pm” into “I got a heads-up at 11:06 and could say something first.”
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 it a URL or drop in a small JS snippet and it will watch that too. So a quiet stall on your own side surfaces the same way, in one place, alongside everything else you build on.
To be clear about what it does not do: NoCrash reads the tool’s own public status page. It does not find the outage before the tool reports it. It catches the report within a minute and tells you in plain English, which is usually well before a customer gets around to complaining.
The official source
For the authoritative account of this outage, go to Bolt.new’s own status page: https://status.bolt.new/proxy/status.bolt.new