Bolt.new had a significant problem starting at 23:00 UTC on July 24, 2026. It lasted about 59 minutes and was resolved by 00:00 UTC on July 25. Bolt.new has since reported the issue as resolved.
Who this kind of outage hits
If you build or ship something on Bolt.new, a problem like this stops your work cold. The hard part is that nothing inside the tool usually tells you. There is no alert, no red banner, no email. You find out because a customer tries something, it does not work, and they message you. By then the outage may already be over, but the damage to trust is done. That gap between “it broke” and “I found out” is where most of the pain lives.
Why it is especially rough if you are not an engineer
An engineer can pull logs, check error traces, and at least feel like they are doing something. If you are running a business on top of a tool like Bolt.new and something goes quiet, you have none of that. The work just stops moving. A form does not submit, a build does not finish, a workflow sits there. The first real signal is often an unhappy customer asking why something is broken. You have no way to tell them when it started, how bad it was, or when it will be fixed. That is a hard conversation to have.
Timeline
- 23:00 UTC, July 24, 2026 - Bolt.new began experiencing a significant problem.
- ~59 minutes - the disruption lasted roughly an hour.
- 00:00 UTC, July 25, 2026 - Bolt.new reported the issue resolved.
How a watcher catches this before your users do
NoCrash reads Bolt.new’s own 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 calm 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 or a small JS snippet you add. 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 problem 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 full and authoritative account of this outage, see Bolt.new’s official status page at https://status.bolt.new/proxy/status.bolt.new.