What happened
Bolt.new had a bigger problem starting October 9, 2026 at 22:31 UTC. It lasted roughly two days, recovering on October 12 at 19:07 UTC. Bolt.new has since reported the issue resolved. No detailed cause has been published beyond that.
Who this hits and how they usually find out
If you build on Bolt.new, you probably were not watching its status page at 10:30 on a Thursday night. Most people find out about an outage like this the slow, painful way: a customer emails to say something is broken, or a client asks why their project looks wrong, or a colleague notices a workflow stopped producing results. By then hours have passed. Sometimes days. The tool was quiet the whole time and nothing inside it told you.
Why this is especially rough if you are not an engineer
There is no error message to read. No log file to open. The work just stops moving and the screen looks normal. You might spend an hour wondering if you did something wrong, retracing your steps, re-checking your settings, before it even occurs to you to look at a status page. And if you do not know where that page is, or that it exists, the first real signal is still an unhappy customer. That gap, between when the tool broke and when you found out, is where trust gets damaged.
Timeline
- October 9, 2026, 22:31 UTC: Bolt.new began experiencing a bigger problem.
- About 2 days of disruption while the issue persisted.
- October 12, 2026, 19:07 UTC: Bolt.new recovered and reported the issue resolved.
How a watcher catches this before your users do
Bolt.new has a public status page. NoCrash reads that page every minute. The moment it flipped from working to having a bigger problem, NoCrash translated that into plain English and sent a heads-up. No jargon, no status codes, just “Bolt.new is reporting a bigger problem right now.” That is the difference between finding out at 22:31 UTC and finding out when a customer writes in two days later.
NoCrash also watches the things you ship on top of Bolt.new. If you have n8n workflows running, it watches those too. If you give it a URL or drop in a small JS snippet, it watches your app directly. So a quiet stall on your own side surfaces the same way, in the same place, in the same plain language.
To be clear about what this is: NoCrash reads the tool’s own public status page. It catches the trouble within a minute of the tool’s own report. It does not find problems before the tool itself knows about them.
For the authoritative account of this outage, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.