On the evening of July 28, 2026, Bolt.new reported a bigger problem starting at 18:05 UTC. It lasted roughly two hours and was resolved at 20:47 UTC. Bolt.new has since confirmed the disruption is over.
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 goes wrong, the first signal is usually a customer writing in to say something is broken, or a collaborator asking why nothing is loading. By that point the outage has already been running for a while. You are now behind, explaining a problem you did not know existed, to someone who found out before you did.
That gap, between when the tool stopped working and when you found out, is where the damage happens. Not in the outage itself.
Why this is especially rough without a technical background
When a tool like Bolt.new has trouble, there is no error message waiting for you. Nothing on your screen changes. Your work just stops moving forward and you do not know why. You might refresh a few times, wonder if it is your internet, or assume you did something wrong. Meanwhile, anything that depended on Bolt.new being available is quietly stalled. The first real signal is often an unhappy person on the other end of whatever you built. At that point you are scrambling to explain something you are only just learning about yourself.
Timeline
- 18:05 UTC, July 28, 2026: Bolt.new reports a bigger problem begins.
- About 2 hours of disruption.
- 20:47 UTC, July 28, 2026: Bolt.new reports the problem is resolved.
How a watcher catches this before your users do
NoCrash reads Bolt.new’s public status page every minute. The moment Bolt.new flips that page 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 turns “my customer told me an hour in” into “I got a heads-up within a minute of Bolt.new’s own report.”
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 alongside anything happening at the tool level. One place, plain English, before the complaints start.
What it does not do: it does not find the outage before Bolt.new’s own status page does. It reads what Bolt.new publishes, as fast as it can, and tells you in language you can actually use.
For the authoritative account of this outage, go to Bolt.new’s official status page: https://status.bolt.new/proxy/status.bolt.new