On the evening of July 25, 2026, Bolt.new reported a bigger problem starting at 21:40 UTC. It lasted about 29 minutes and was marked resolved at 22:10 UTC. Bolt.new has since confirmed the disruption is over.
who this kind of outage hits
If you build on Bolt.new, you are probably not watching its status page while you work. Most people are not. So when something goes wrong, the first signal is often a customer writing in to say something is broken, or a collaborator asking why a project will not load. By the time that message arrives, the outage may already be over, but the damage to trust is done. You are left explaining something you did not know about, to someone who noticed before you did.
why it is especially rough without a technical background
There is no error log to open. There is no red alert on your screen. The work just stops, quietly, and you have no way to tell whether it is your connection, your browser, your project, or the tool itself. That uncertainty is its own kind of stress. You start second-guessing your own setup before you even think to check whether the tool is having trouble. The first hard signal is usually an unhappy person on the other end.
timeline
- 21:40 UTC, July 25, 2026: Bolt.new reports a bigger problem begins.
- About 29 minutes of disruption.
- 22:10 UTC, July 25, 2026: Bolt.new marks 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 check anything yourself. 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 also watches the specific things you ship: your n8n workflows through an API token, and your app 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. NoCrash does not find the outage before Bolt.new’s own status page does. It just makes sure you hear about it right away, in plain English, in one place.
For the authoritative account of this disruption, see Bolt.new’s own status page at https://status.bolt.new/proxy/status.bolt.new.