On July 30, 2026, Bolt.new reported a bigger problem starting at 12:12 UTC. It lasted about four hours and was resolved at 16:32 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, a four-hour window where things are not working properly is a long time for something to go wrong quietly. Most operators find out the same way: a customer writes in, confused or annoyed, and only then does the operator start digging. By that point the damage is already done. There was no alert, no warning, nothing inside the tool that said “stop, something is wrong.” The work just stopped moving and nobody told you.
Why this is especially rough without a technical background
When you are not an engineer, a quiet outage is the worst kind. There are no logs to read, no error message on your screen, no obvious sign that the tool itself is the problem. You might spend time wondering if you did something wrong, checking your own setup, maybe even apologizing to a customer before you realize the tool was the issue all along. The first real signal is an unhappy person, and that is a bad way to find out.
What the timeline looked like
- 12:12 UTC – Bolt.new reported a bigger problem starting
- About 4 hours – the disruption continued
- 16:32 UTC – Bolt.new confirmed the issue was 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 yourself. That turns “my customer told me something was broken” into “I got a calm heads-up within a minute of Bolt.new’s own report.” It also watches the specific things you ship: your n8n workflows through an API token, and your app through a URL or a small JS snippet you add. So if something goes quiet on your own side, that surfaces too, sitting next to everything else you build on. NoCrash does not find the outage before Bolt.new’s own status page does. It reads that page and tells you fast, in plain English, in one place.
For the authoritative account of this outage, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.