what happened
Bolt.new reported a bigger problem starting June 5, 2026 at around 15:00 UTC. It lasted roughly two days, recovering on June 8 at 10:04 UTC. Bolt.new has since marked the issue resolved. The details of what caused it are not something we can speak to, and we won’t guess.
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, or you are asleep, or you are doing something else entirely. A two-day disruption on a tool you depend on does not announce itself with a siren. It just stops working quietly. The first sign is usually a customer writing in to say something is broken, or a colleague asking why a project link isn’t loading. By then the outage has already been running for hours, sometimes longer. You are now explaining a problem you didn’t know existed, to someone who noticed before you did.
why this is especially rough without a technical background
If you are not an engineer, there is no log file to open, no error trace to read, no alert firing somewhere in a system you control. The work just stops moving. A build that should have finished hasn’t. A link that should load doesn’t. Nothing on your screen tells you why. You start wondering if you did something wrong, if it’s your browser, if it’s your account. You spend time troubleshooting something that was never yours to fix. Then, eventually, you find the status page, or a customer finds you first. Two days is a long time to be in that position.
timeline
- Started: June 5, 2026 at 15:00 UTC
- Lasted: approximately 2 days
- Recovered: June 8, 2026 at 10:04 UTC
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, NoCrash sends a plain-language message explaining what it sees, in words that don’t require a technical background to act on. You don’t have to be watching the status page yourself. You don’t have to wait for a customer to tell you.
For a two-day disruption like this one, that difference matters. Knowing within a minute of Bolt.new’s own public report means you can reach out to affected users yourself, set expectations, and stop spending time wondering what went wrong on your end. It also means the message sits next to everything else you build on, so you are not juggling five different status pages across five different tabs.
NoCrash also watches the things you ship. If you have n8n workflows, it watches those runs. If you have an app, it watches it through a URL you provide or a small JS snippet you add. So if something goes quiet on your own side, that surfaces too, separately from what any underlying tool is reporting.
None of this finds the problem before Bolt.new’s own status page does. It just means you hear about it right away, in plain English, in one place, instead of hearing it from a customer first.
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.