What happened
Bolt.new reported a bigger problem starting at 04:01 UTC on July 27, 2026. It lasted about 9 minutes and was resolved at 04:11 UTC. The disruption is over, and Bolt.new has marked it resolved.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, a nine-minute window of trouble can feel invisible at first. Your project stalls, a build hangs, something just does not go through. You are not watching a status page at 4 in the morning. Most people find out the wrong way: a user messages them, a client asks why something is broken, or they stumble on it themselves an hour later while wondering why a task never finished. The tool did not send you anything. Nothing in your workflow flagged it. You were just the last to know.
Why this is especially rough if you are not an engineer
There are no logs to pull. There is no error message sitting on a screen waiting for you. The work simply stops moving, quietly, and the first real signal is an unhappy person on the other end. An engineer might check a status page out of habit. A solo founder or automation operator usually does not, because there are twenty other things open. By the time the picture becomes clear, the disruption is already over and the damage, a missed deadline, a confused customer, a broken demo, is already done.
Timeline
- 04:01 UTC, July 27, 2026 - Bolt.new’s status page showed a bigger problem.
- 04:11 UTC, July 27, 2026 - Bolt.new marked the disruption resolved.
- Total duration - about 9 minutes.
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 looking. That is the difference between “my customer just told me something is broken” and “I got a quiet heads-up a minute after Bolt.new’s own page reported it.”
It also watches the things you ship. If you have n8n workflows, NoCrash watches those too. If you give it a URL or drop in a small JS snippet, it watches your app. So if the trouble is on your side rather than Bolt.new’s side, that surfaces as well. NoCrash does not claim to find problems before the tool’s own status page does. It reads that page and tells you right away, in one place, alongside everything else you build on.
For the authoritative account of this outage, see Bolt.new’s official status page: https://status.bolt.new/proxy/status.bolt.new