On July 16, 2026, Bolt.new reported a bigger problem starting at 09:05 UTC. It lasted about four hours and was resolved at 13:32 UTC. Bolt.new has since confirmed the disruption is over.
Who this kind of outage hits
If you build or run something on Bolt.new, you probably found out the wrong way. Not from a log, not from an alert. From a customer saying something felt broken, or from noticing yourself that a project you expected to be moving had gone quiet. That gap, between when the tool stopped working and when you heard about it, is where the damage happens. A paying customer files a complaint, a deadline slips, and you are left explaining something you did not even know was happening.
Why it is especially rough without a technical background
When you are not an engineer, there is no place to look. No server log to pull, no error trace to read. The work just stops moving and the screen looks normal. The first real signal is usually a frustrated message from someone who was counting on you. By then you are already behind, already apologizing, already trying to explain an outage you learned about from the person it hurt.
What the timeline looked like
- 09:05 UTC Bolt.new reported a bigger problem.
- 09:05 to 13:32 UTC The disruption continued for about four hours.
- 13:32 UTC Bolt.new confirmed the issue was resolved.
That is roughly a full morning of work affected, with no warning built into the tool itself.
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, sitting next to everything else you build on. You do not have to check anything. You do not have to wait for a customer to tell you.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those too. If you have an app, you can give it a URL or drop in a small JS snippet and it will watch that as well. So a quiet stall on your own side surfaces the same way, in the same place.
To be straight about what this is: NoCrash catches the trouble within a minute of Bolt.new’s own public 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, instead of hearing about it from a customer two hours later.
For the authoritative account of this outage, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.