Bolt.new had a bigger problem starting June 16, 2026 at around 14:10 UTC. It lasted about five days, recovering on June 22 at 08:42 UTC. Bolt.new has since marked it resolved. That is the full picture the official status page gives us, and this postmortem stays inside those lines.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, you are probably not watching its status page. You are building, shipping, talking to customers. The first sign something is wrong is usually a customer message: a project that will not load, a feature that stopped working, a reply that says “is this thing broken?” That gap, between when the tool stopped and when a customer told you, is where the damage happens. You spend the next hour trying to figure out if it is your code, your setup, or the tool itself. It is the tool. It was the tool for days.
Why five days of quiet trouble is especially rough
There is no error on your screen. Nothing in Bolt.new tells you it is struggling. Your work just stops moving forward, or your users hit walls you cannot see. You have no logs to read, no alert to act on. The silence is the problem. For a non-engineer running a product on a platform like this, the only feedback loop is an unhappy customer, and by the time that message arrives, the trust is already a little dented.
Five days is a long time to be in the dark.
A short timeline
- Started: June 16, 2026 at 14:10 UTC
- Lasted: about 5 days
- Recovered: June 22, 2026 at 08:42 UTC
- Status: resolved, per Bolt.new’s own page
How a watcher catches this before your users do
Bolt.new has a public status page. NoCrash reads it every minute. The moment it flips from working to having a bigger problem, NoCrash sends you a plain-language message, in words you can act on, without you having to go check anything yourself.
That is the honest version of what it does. It does not find the outage before Bolt.new reports it. It catches the report within a minute of Bolt.new’s own update and puts it in front of you in plain English, sitting next to everything else you build on.
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 your own side goes quiet separately, that surfaces too. The combination means fewer “a customer just told me” moments.
For the authoritative account of this outage, go to the official Bolt.new status page: https://status.bolt.new/proxy/status.bolt.new