On July 22, 2026, Bolt.new had a significant disruption starting at 15:30 UTC. It lasted about 43 minutes and was resolved by 16:13 UTC. Bolt.new has since reported it resolved. That is the full picture the official source gives us right now.
Who this kind of outage hits, and how they usually find out
If you build something on Bolt.new, you probably are not watching its status page while you work. Most people are not. So when the tool goes quiet in the middle of the afternoon, the first signal is often a customer message. “Hey, this isn’t working.” Or a collaborator asking why a build is stuck. By the time that message arrives, the disruption may already be over, but the damage to trust is done. You are now explaining something you did not know about, to someone who noticed before you did.
That gap, between when the tool stopped working and when you found out, is the part that stings.
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 project that was building fine an hour ago now sits there. You refresh. You try again. You wonder if it is something you did. Meanwhile, anyone depending on what you are building is already confused. The first real signal is an unhappy person, not a system alert. That is a hard way to find out.
What the timeline looked like
- 15:30 UTC - Bolt.new began experiencing a bigger problem.
- 15:30 to 16:13 UTC - The disruption continued for about 43 minutes.
- 16:13 UTC - Bolt.new reported the issue resolved.
How a watcher catches this before your users do
Bolt.new, like most tools, has a public status page. It updates that page when something goes wrong. NoCrash reads that page every minute. The moment it flips from working to having trouble, NoCrash sends you a plain-language message saying what broke and when, in words you can act on without being an engineer.
That is the shift. Instead of a customer telling you, you get a calm heads-up first. You can post a quick note, pause a campaign, or just know what is happening before anyone asks.
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 your own side goes quiet separately, that surfaces too, in the same place.
To be straight about what this is: NoCrash reads the tool’s own public report. It does not find the outage before Bolt.new reports it. It catches it within a minute of that report and tells you in plain English, which is usually well before a customer notices and writes to you.
For the authoritative account of this outage, go to the official Bolt.new status page: https://status.bolt.new/proxy/status.bolt.new