what happened
Bolt.new reported a bigger problem starting at 23:30 UTC on June 13, 2026. The disruption lasted about four hours and was resolved by 03:42 UTC on June 14. Bolt.new has since confirmed the issue is resolved. The facts available are thin, so this piece stays honest about that and focuses on the shape of the problem rather than inventing detail.
who this hits and how they usually find out
If you build on Bolt.new, your projects, prototypes, or client work live inside it. When it stops working, nothing inside the tool tells you. There is no alert, no email, no red banner that says “your work is paused.” You find out when a client tries to open something you sent them, or when a customer emails to say the thing you built is broken. That gap, between when the tool went quiet and when someone complained, is where the damage happens. A four-hour window overnight is long enough for a client in a different time zone to hit a wall and start wondering whether you know what you are doing.
why this is especially rough without a technical background
A developer can pull up logs and see that requests failed at a specific time. You probably cannot. What you see is that something stopped working, and you have no way to know if it is your fault, the tool’s fault, or something else entirely. That uncertainty is its own kind of stress. You start second-guessing your last change. You wonder if you broke something. Meanwhile the real answer is simply that the tool had a bad night, and there was nothing you could have done. The first signal most people get is an unhappy customer, which is the worst possible way to learn about someone else’s problem.
timeline
- June 13, 2026 at 23:30 UTC, Bolt.new reported a bigger problem on its public status page.
- The disruption lasted about four hours.
- June 14, 2026 at 03:42 UTC, Bolt.new marked 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 flipped from working to reporting a bigger problem, NoCrash would have sent a plain-language heads-up, in words that do not require a technical background to act on. That happens within a minute of Bolt.new’s own report, which is as fast as it is possible to know from the outside.
That heads-up sits alongside everything else you build on. If you run n8n workflows, NoCrash watches those too, so a quiet stall on your automation side surfaces the same way. If you have an app or a URL you care about, you can give NoCrash that address or drop in a small JS snippet, and it watches that as well. The goal is simple: you hear about a problem in plain English, in one place, before a customer does. Not because NoCrash knows something the tool does not, but because it is paying attention so you do not have to be.
the authoritative account
For the official record of this outage, see Bolt.new’s own status page at https://status.bolt.new/proxy/status.bolt.new.