On July 25, 2026, Bolt.new reported a bigger problem starting at 12:36 UTC. It lasted about 25 minutes and was resolved at 13:01 UTC. Bolt.new has since confirmed the disruption is over.
Who this kind of outage hits
If you build on Bolt.new, you probably are 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 link stopped loading. 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
When a tool like Bolt.new goes quiet, there is no error on your screen. No log file. No alert. The work just stops moving. If you were mid-build, you might spend time wondering whether you did something wrong, whether it is your browser, whether you should try again or wait. That uncertainty is its own cost, separate from the outage itself. The first hard signal is usually an unhappy person on the other end, and by then you are already behind.
What the timeline looked like
Bolt.new reported a bigger problem at 12:36 UTC on July 25, 2026. The disruption lasted about 25 minutes. Service recovered at 13:01 UTC. Bolt.new has marked the issue as 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 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 things you ship: your n8n workflows through an API token, and your app through a URL or a small JS snippet you add. So if something goes quiet on your 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 reads that page and tells you fast, in plain English, in one place.
For the authoritative account of this outage, see Bolt.new’s official status page at https://status.bolt.new/proxy/status.bolt.new.