Bolt.new had a bigger problem starting July 9, 2026 at 04:41 UTC. It lasted about 22 hours and recovered on July 10 at 03:05 UTC. Bolt.new has since marked it resolved. No detailed cause has been published.
Who this kind of outage hits, and how they usually find out
If you build something on Bolt.new, a 22-hour stretch of bigger problems is a long time for things to go quietly wrong. Most people find out the same way: a customer writes in, confused or annoyed, and only then does the builder start digging. By that point the disruption has already done its damage. The tool itself rarely sends you a plain-English message saying “hey, something is wrong right now.” You have to go looking, and most people are not looking at a status page every hour.
Why this is especially rough if you are not an engineer
There is no error on your screen. There is no log file to open. The work just stops moving, or slows down in ways that are hard to name. A form stops submitting. An automation goes quiet. A build does not finish. You might assume it is something you did, spend time second-guessing yourself, and only later realize the tool itself was the problem. The first real signal is often an unhappy customer, and by then you are already behind.
What the timeline looked like
- Started: July 9, 2026 at 04:41 UTC
- Recovered: July 10, 2026 at 03:05 UTC
- Total duration: about 22 hours
- Status: resolved, per Bolt.new’s own status page
That is a long window. Anything you or your customers tried to do with Bolt.new during that stretch ran into bigger problems.
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 gap between “something is wrong” and “you find out” is usually just the time between that update and whenever you happen to check.
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, in one place, alongside everything else you build on. You find out within a minute of Bolt.new’s own report, in words you can act on, not status-page jargon.
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, separately from what the tool is reporting.
To be straight about what this is: 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, so you are not the last to know.
The authoritative account
For the official record of this outage, go to Bolt.new’s status page: https://status.bolt.new/proxy/status.bolt.new