Bolt.new had a significant outage starting at 21:55 UTC on July 6, 2026. It lasted about 9 hours and was resolved at 07:38 UTC on July 7. Bolt.new has since reported the issue resolved, but has not published a detailed cause.
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. An overnight outage like this one is especially cruel because it runs while you sleep. You wake up to a message from a user asking why something is broken, and that message is your first signal. Not an alert. Not a warning. A confused or frustrated customer. That is the normal shape of this problem, and it happens to careful, attentive operators all the time.
Why this is rough without any technical background
There is no error on your screen. Nothing in Bolt.new tells you the tool itself is the problem. Your work just stops moving. If you have automations or workflows that depend on Bolt.new, they go quiet. If your app relies on something Bolt.new powers, it stalls. You have no logs to read, no red light to point at. The first real signal is a customer who noticed before you did, and by then the outage may have been running for hours.
What the timeline looked like
- Outage started: July 6, 2026 at 21:55 UTC
- Outage resolved: July 7, 2026 at 07:38 UTC
- Total duration: about 9 hours
The disruption ran through the night across most European time zones and through the evening on the US East Coast.
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 a problem, NoCrash sends you a plain-language message explaining what is going on, in words you can act on, without needing to interpret anything technical. You find out within a minute of Bolt.new’s own public report, not hours later from a customer.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those too. If you have an app, you can give NoCrash a URL or drop in a small JS snippet, and it will watch that as well. So if the problem is on your side rather than Bolt.new’s side, that surfaces too, in the same place.
To be straight about what this is: NoCrash reads what Bolt.new publicly reports. It does not find the outage before Bolt.new’s own status page does. What it does is make sure you are not the last to know.
For the authoritative account of this outage, see Bolt.new’s official status page at https://status.bolt.new/proxy/status.bolt.new.