Bolt.new had a significant disruption on June 23, 2026. It started at 02:04 UTC, lasted roughly an hour, and was resolved by 04:01 UTC. Bolt.new has since reported the issue as resolved.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, you probably were not watching it at 2 in the morning. You woke up, opened your laptop, and either things looked fine or a customer had already messaged you asking why something was broken. That gap, between when the tool stopped working and when you heard about it, is where the damage happens. A paying customer noticed before you did, and now you are explaining yourself instead of just fixing things.
This is the normal shape of a quiet outage. Nothing sends you an alert. Nothing inside Bolt.new tells you your work stopped. You find out from someone who was affected.
Why this is especially rough if you are not an engineer
An engineer can pull logs, check error traces, piece together a timeline. If you are a solo founder or an automation operator, none of that is available to you. You just see that something is not working, or worse, you do not even see that. The work stops moving silently. No red screen, no warning, no message. The first signal is an unhappy customer, and by then you are already behind.
That is not a personal failure. It is just how these tools work. They do not push alerts to the people building on them.
Timeline
- 02:04 UTC, June 23, 2026 - Bolt.new began experiencing a bigger problem.
- About one hour - the disruption lasted roughly 57 minutes.
- 04:01 UTC, June 23, 2026 - Bolt.new reported the issue resolved.
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, in words you can act on, without you having to go check anything yourself.
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 NoCrash will watch that as well. So if your own side goes quiet separately from Bolt.new, that surfaces too, in the same place.
To be clear about what this is: NoCrash catches the trouble within a minute of Bolt.new’s own public report. It does not find the outage before Bolt.new reports it. What it does is make sure you hear about it in plain English, fast, instead of hearing about it from a customer.
For the authoritative account of this outage, see Bolt.new’s official status page: https://status.bolt.new/proxy/status.bolt.new