What happened
Bolt.new had a significant outage starting June 9, 2026 at around 15:14 UTC. It lasted about three days, recovering on June 12 at roughly 15:30 UTC. Bolt.new has since reported the issue resolved. The status note gives no detail on root cause, so neither do we.
Who this hits and how they usually find out
If you build on Bolt.new, a three-day disruption is not a blip. It is a week of work, half a sprint, a product demo gone wrong. Most people who build on tools like this find out the same way: a customer writes in, confused or annoyed, asking why something is broken. Not an alert. Not a warning. A frustrated message from someone who was counting on the thing working. By the time that message arrives, the disruption has often been running for hours, sometimes longer. You were the last to know, and the first to apologize.
Why this is especially rough without an engineering team
If you have engineers, someone is probably watching logs somewhere. If you are a solo founder or a small team running automations, there are no logs to read. There is no error on the screen. The work just stops moving. A workflow that should have fired at 9 a.m. did not fire, and you will not know that until someone downstream notices the silence. The gap between “something went wrong” and “I found out” is filled entirely by your customers’ patience, which is not infinite. Three days is a long time to be in the dark.
Timeline
- June 9, 2026, 15:14 UTC, the disruption began.
- It ran for approximately three days.
- June 12, 2026, 15:30 UTC, Bolt.new reported it 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, it sends you a plain-language message, in words you can act on, not a raw status code. That does not mean NoCrash finds the problem before Bolt.new does. It means you hear about it within a minute of Bolt.new’s own public report, instead of whenever a customer gets around to telling you.
It also watches the things you ship on top of tools like this. Your n8n workflows, your app through a URL you give it or a small snippet of code. So if your own side goes quiet, that surfaces too, separately from whatever the underlying tool is reporting. The combination means fewer gaps between “something stopped” and “I know about it.”
None of this replaces Bolt.new fixing the problem. But “I got a calm heads-up and could tell my users something” is a different situation than “a customer told me three days in.”
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.