On July 22, 2026, Bolt.new reported a bigger problem starting at 16:40 UTC. It lasted about an hour and was marked resolved at 17:50 UTC. Bolt.new has since confirmed the disruption is over. The details beyond that are thin, so this piece stays honest about what is actually known.
Who this kind of outage hits
If you build on Bolt.new, you probably are 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 a project will not load. By the time that message arrives, the outage may already be over, but the damage to trust is done. You are left explaining something you did not know was happening.
That gap, between when the tool stopped working and when you found out, is the part that costs you.
Why this is especially hard without a technical background
When a tool like Bolt.new goes quiet, there is no error on your screen telling you why. There is no log to read. The work just stops moving. A build does not finish. A project does not save. You might refresh a few times, wonder if it is your connection, and lose twenty minutes before you even suspect the tool itself is the problem. The first real confirmation often comes from someone else, someone who is already frustrated.
That is not a personal failure. It is just how these tools work when they do not work.
A short timeline
- 16:40 UTC - Bolt.new reports a bigger problem begins
- 17:50 UTC - Bolt.new marks the disruption resolved
- Total duration - about 1 hour
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. Not a raw status code. Not a technical alert. A sentence you can read and act on immediately, sitting next to everything else you build on.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those too. If you have an app, you can give NoCrash a URL or drop in a small JS snippet, and it will watch that as well. So if something goes quiet on your own side, that surfaces too, separately from whatever the underlying tool is doing.
To be clear 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 removes is the gap between Bolt.new knowing and you knowing.
For the authoritative account of this outage, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.