What happened
Bolt.new reported a bigger problem on July 8, 2026, starting at 06:30 UTC. It lasted about 12 minutes and was marked resolved at 06:42 UTC. The official status page says the issue has been resolved, and no further detail has been published.
Who this kind of outage hits, and how they usually find out
If you build something on Bolt.new, a short disruption like this can stop your work cold without making any noise. No alert fires. No email lands. You are usually heads-down on something else, and the first sign anything went wrong is a customer writing in to say their thing is broken, or a collaborator asking why nothing is moving. By then the outage is already over, but the damage to trust is done. Twelve minutes feels short until it is the twelve minutes a new customer tried your product for the first time.
Why this is especially rough without a watcher
If you are not an engineer, there is nothing to inspect. No logs, no error screen, no red light on a panel you own. The work just stops moving. You cannot tell whether the problem is on Bolt.new’s side, your side, or somewhere in between. So you wait, or you start poking at things that are not broken, or you find out from someone who is already frustrated. That is the shape of almost every quiet outage for a solo operator or a small team.
Timeline
- 06:30 UTC, July 8, 2026 - Bolt.new’s status page reported a bigger problem.
- 06:42 UTC, July 8, 2026 - Bolt.new marked the issue resolved.
- Total duration - about 12 minutes.
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 you a plain-language message, in words you can act on, without you having to go check anything yourself. For an outage like this one, that means you would have known within a minute of Bolt.new’s own report, not from a frustrated customer twenty minutes later.
NoCrash also watches the things you ship. If you have n8n workflows, it watches those through your API token. If you have an app, it watches it through a URL you give it or a small JS snippet you drop in. So if something goes quiet on your own side, that surfaces too, sitting next to everything else you build on. It does not decide on its own whether a third-party tool is healthy before that tool says so. It reads what the tool reports, and tells you fast, in one place.
For the authoritative account of this outage, see the official Bolt.new status page: https://status.bolt.new/proxy/status.bolt.new