On the morning of July 25, 2026, Bolt.new reported a bigger problem starting at 09:06 UTC. It lasted about 8 minutes and was resolved by 09:14 UTC. Bolt.new has since confirmed the disruption is over. No detailed cause has been published.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, your projects and workflows depend on it being available. When it goes quiet, nothing inside your setup tells you. There is no alert, no red banner, no message. You find out because a customer tries something, it does not work, and they write to you. By then you have already lost time and credibility. The gap between “it stopped working” and “I found out” is almost always filled by an unhappy person on the other end.
Why this is especially rough if you are not an engineer
An engineer can pull logs, check error output, and at least see something. If you are running a product or an automation without that background, you have none of that. The work just stops moving. A form does not submit. A workflow does not fire. An app sits there looking fine on the surface while nothing actually happens underneath. The first real signal is a customer complaint, and by then you are already behind.
Timeline
- 09:06 UTC, July 25, 2026 - Bolt.new reports a bigger problem begins.
- 09:14 UTC, July 25, 2026 - Bolt.new reports the disruption is resolved.
- Total duration - about 8 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. That turns “my customer told me something is broken” into “I got a heads-up within a minute of Bolt.new’s own report.” It is not faster than Bolt.new’s own status page, but it means you do not have to be watching that page yourself.
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 the trouble is on your side rather than Bolt.new’s, that surfaces too, in the same place.
Eight minutes is short. But if those eight minutes overlap with a customer demo, a campaign going out, or a workflow that runs on a schedule, short is long enough to matter.
For the authoritative account of this outage, see the official Bolt.new status page at https://status.bolt.new/proxy/status.bolt.new.