On the morning of August 31, 2026, Bolt.new reported a bigger problem starting at 09:21 UTC. It lasted about 32 minutes and was resolved by 09:53 UTC. Bolt.new has since confirmed the issue is resolved. No detailed cause has been published beyond that.
Who this kind of outage hits
If you build on Bolt.new, you probably found out about this one of two ways: you happened to be working in the tool right when it went wrong, or a customer or colleague told you something was broken. Most people fall into the second group. The tool goes quiet, nothing obvious breaks on your screen, and the first real signal is an email or a message that says “hey, is this supposed to work?” By then you are already behind, already explaining yourself, already losing the trust you spent time building.
Why it is especially rough without a technical background
A software engineer can pull up logs, check error messages, and at least confirm the problem is not on their side. A solo operator or a non-engineer founder does not have that. The work just stops moving. A form stops submitting, a workflow stops running, an app goes blank, and there is no red warning anywhere. You start second-guessing yourself. You wonder if you broke something. You spend twenty minutes checking the wrong things before you think to look at whether the tool itself is having trouble. By the time you find the status page, the outage may already be over, and you still have no idea how long your users were affected.
Timeline
- 09:21 UTC - Bolt.new reports a bigger problem begins.
- 09:53 UTC - Bolt.new reports the issue is resolved.
- Total duration - about 32 minutes.
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 saying what broke and when. You do not have to find the status page yourself. You do not have to wait for a customer to tell you. You get a calm heads-up in plain English, sitting next to everything else you build on, within a minute of Bolt.new’s own report.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those too. If you have an app, you can give it 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 in the same place.
To be clear about what this is: NoCrash reads public status pages and watches the specific things you point it at. It does not find outages before the tool’s own status page does. But it means you are reading that status page every minute without having to think about it.
For the authoritative account of this outage, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.