What happened
Bolt.new had a significant disruption on July 29, 2026, starting at 15:15 UTC. It lasted about one hour and was resolved at 16:25 UTC. Bolt.new has since reported the issue resolved. No detailed cause has been published at the time of writing.
Who this hits and how they usually find out
If you build on Bolt.new, you probably were not staring at its status page at 15:15 on a Tuesday. You were doing something else. The first sign something was wrong was likely a message from a user, a client, or a colleague asking why something was broken or slow. That gap, between when the tool stopped working and when a real person told you, is where the damage happens. A customer who hits a wall and gets no explanation does not wait around. They form an opinion, and it is not a generous one.
Why this is especially rough if you are not an engineer
There is no error log to open. Nothing on your screen says “Bolt.new is having trouble.” The work just stops moving. A build does not finish. A project does not load. You might spend twenty minutes wondering if you did something wrong before it even occurs to you to check whether the tool itself is the problem. By then, someone downstream has already noticed. That is the quiet part of a quiet outage: the silence feels like your fault until it does not.
Timeline
- 15:15 UTC - Bolt.new began experiencing a bigger problem.
- 15:15 to 16:25 UTC - The disruption continued for about one hour.
- 16:25 UTC - Bolt.new reported the issue resolved.
How a watcher catches this before your users do
Bolt.new, like most tools, publishes a public status page. When something goes wrong, they update it. The problem is that nobody is refreshing that page every minute while also running a business.
NoCrash reads Bolt.new’s public status page every minute. The moment it flips from working to having trouble, NoCrash sends you a plain-language message explaining what is going on, in words you can act on, without needing to interpret anything technical. It catches the change within a minute of Bolt.new’s own report. That is not magic, it is just consistent attention you do not have to pay yourself.
NoCrash also watches the things you ship: your n8n workflows through an API token, and your app through a URL you give it or a small JS snippet. So if something goes quiet on your own side, that surfaces too, sitting next to everything else you build on.
The result is that “my customer told me” becomes “I got a calm heads-up first, and I already knew what was happening.”
For the authoritative account of this outage, see the official Bolt.new status page: https://status.bolt.new/proxy/status.bolt.new