Bolt.new had a significant outage starting June 30, 2026 at 22:35 UTC. It lasted about five days, recovering on July 6 at 16:37 UTC. Bolt.new has since marked the issue resolved. The status note gives no further detail on what went wrong.
Who this hits and how they usually find out
If you build on Bolt.new, you probably found out the wrong way: a customer messaged you, a client asked why their app looked broken, or you noticed something felt off and started poking around. That is the normal shape of this kind of thing. The tool goes quiet, nothing inside it screams at you, and the first real signal is someone else’s frustration landing in your inbox. Five days is a long time to be in the dark.
Why it is especially rough if you are not an engineer
There are no logs to read. There is no red error on your screen. The work just stops moving. If you have automations running on Bolt.new, they may have stalled silently. If your app lives there, visitors may have hit a broken page while you were doing something else entirely. You have no way to know unless you happened to check at the right moment, or unless someone told you. Most people get told by a customer. That is a bad position to be in, especially across a five-day window.
What the timeline looked like
- Started: June 30, 2026 at 22:35 UTC
- Lasted: about 5 days
- Recovered: July 6, 2026 at 16:37 UTC
- Status: resolved, per Bolt.new’s own status page
How a watcher catches this before your users do
Bolt.new has a public status page. When something goes wrong, they post there. The gap between “the tool is having trouble” and “you find out” is usually just however long it takes someone to check that page, which for most people is never, or too late.
NoCrash reads that status page every minute. The moment Bolt.new’s own page flips from working to having trouble, NoCrash sends you a plain-language message telling you what is going on, in words you can act on, without you having to go looking. It also watches your n8n workflows directly, and your app through a URL you give it or a small JS snippet, so if something on your own side goes quiet, that surfaces too. None of this replaces Bolt.new’s own reporting. It just means you hear about it in plain English, in one place, within a minute of Bolt.new saying so themselves, instead of from a frustrated customer five days later.
For the authoritative account of this outage, see Bolt.new’s official status page: https://status.bolt.new/proxy/status.bolt.new