On June 25, 2026, Bolt.new experienced a significant disruption starting at 14:35 UTC. It lasted about four hours, recovering at 18:52 UTC. Bolt.new has since reported the issue resolved. No detailed cause has been published at the time of writing.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, your projects, your automations, your whole workflow can go quiet without a single alert reaching you. The tool does not call you. There is no pop-up, no email, no red banner in your inbox. What usually happens instead is that a customer tries something, it does not work, and they message you. By then the outage has already been running for an hour or two. You are now explaining a problem you did not know existed, to someone who is already frustrated.
That gap, between when the tool stops working and when you find out, is where trust gets damaged. Not because you did anything wrong, but because you had no way to know.
Why this is especially rough if you are not an engineer
An engineer can go digging. They can check logs, trace a request, read an error. A non-engineer operator has none of that. You open the tool, something does not load or a run does not finish, and there is nothing to read. The work just stops moving. The first real signal is often a customer asking why their thing is broken. You are left trying to figure out whether the problem is on your side or theirs, with no information to go on. Four hours is a long time to be in that position.
Timeline
- 14:35 UTC, June 25, 2026 - Bolt.new begins experiencing a bigger problem.
- Roughly 14:35 to 18:52 UTC - The disruption continues for about four hours.
- 18:52 UTC, June 25, 2026 - Bolt.new recovers and reports the issue 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, NoCrash sends you a plain-language message, in words you can act on, without you having to go looking. That is not the same as finding the problem before Bolt.new does. It means you hear about it within a minute of Bolt.new’s own report, instead of an hour later when a customer tells you.
NoCrash also watches the specific things you ship. If you have n8n workflows, it watches those. If you have an app, you can give it a URL or drop in a small JS snippet, and it will watch that too. So if something goes quiet on your own side, that surfaces as well, sitting next to everything else in one place.
The result is that “my customer told me” becomes “I got a calm heads-up first, and I knew what was happening before anyone asked.”
For the authoritative account of this outage, see Bolt.new’s official status page at https://status.bolt.new/proxy/status.bolt.new.