On July 29, 2026, Bolt.new reported a bigger problem starting at 08:35 UTC. It lasted about three hours and was resolved at 11:47 UTC. Bolt.new has since confirmed the disruption is over.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, your apps and workflows depend on it quietly working in the background. When it stops, nothing inside your setup throws an alert. No red banner, no email, no pop-up. The work just stops moving. Most operators find out the same way: a customer writes in asking why something is broken, or a client notices the app is behaving strangely. By then the outage has already been running for a while, and you are playing catch-up while also trying to explain yourself to someone who paid you.
Why this is especially rough if you are not an engineer
An engineer can pull logs, check error traces, and at least confirm what broke. If you are running your business on these tools without that background, you have none of that. The screen looks normal. The tool might even load fine. But the work has quietly stopped, and there is no obvious place to look. The first real signal is an unhappy customer, and that is a terrible way to find out your stack has been broken for two hours.
What the timeline looked like
Bolt.new reported a bigger problem at 08:35 UTC on July 29, 2026. The disruption ran for about three hours. It was resolved at 11:47 UTC the same morning.
How a watcher catches this before your users do
NoCrash reads Bolt.new’s own public status page every minute. The moment that page flips from working to having trouble, NoCrash sends you a plain-language message explaining what is going on, in words you can act on immediately. You do not have to check the status page yourself, remember the URL, or piece together what “degraded performance” means at 8 in the morning.
On top of that, NoCrash 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 own side rather than Bolt.new’s, that surfaces too.
The honest limit: NoCrash reads Bolt.new’s status page and tells you within a minute of Bolt.new’s own report. It does not find the outage before Bolt.new does. What it does is make sure you hear about it in plain English, right away, in one place, instead of hearing it first from a frustrated customer.
For the authoritative account of this outage, see Bolt.new’s official status page: https://status.bolt.new/proxy/status.bolt.new