What happened
Bolt.new had a significant disruption on September 21, 2026, starting at 11:00 UTC. It lasted about 12 minutes and was resolved by 11:13 UTC. Bolt.new reports the issue is now resolved. The disruption was described as a bigger problem, meaning it was more than a minor hiccup.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, a 12-minute window where things go wrong can quietly swallow a customer’s work, a scheduled run, or a key part of your product. The frustrating part is that you probably would not have known in the moment. Most people find out the same way: a customer messages them, confused or annoyed, and only then does the scramble begin. You check the tool, it looks fine now, and you spend the next hour piecing together what happened and when. That gap between “it broke” and “I heard about it” is where trust gets damaged.
Why this is especially rough without a technical background
When something like this happens, there is no error message waiting for you. No log file to open. The work just stops moving, quietly, and nothing on your screen tells you why. If you are not an engineer, you have no obvious place to look. The first real signal is often a confused customer or a missed delivery. By then the tool has already recovered, and you are left explaining something you did not know was happening.
Timeline
- 11:00 UTC - Bolt.new starts experiencing a bigger problem.
- 11:13 UTC - Bolt.new reports the issue resolved.
- Total duration - about 12 minutes.
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 that hurts you is the time between that update and the moment you happen to check, which could be hours if you are heads-down on other work.
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 explaining what is going on, in one place alongside everything else you build on. You do not need to be watching the status page yourself. You do not need a customer to tell you first.
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’s status page says.
What it does not do is find the outage before Bolt.new’s own status page reports it. The speed comes from reading that page constantly, not from any independent detection. For a 12-minute disruption like this one, that difference matters.
The authoritative account
For the official record of this disruption, see Bolt.new’s own status page at https://status.bolt.new/proxy/status.bolt.new.