On the evening of July 24, 2026, Bolt.new reported a bigger problem starting at 21:40 UTC. It lasted about 19 minutes and was resolved by 22:00 UTC. Bolt.new has since marked it as resolved, with no detailed cause published at this time.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, a short disruption like this can stop your work cold without any obvious signal. You might be mid-build, or you might have a workflow running in the background that you are not watching at that exact moment. The way most people find out is not from the tool itself. It is from a customer asking why something is broken, or from noticing hours later that a task never finished. That gap, between when the tool stopped and when you realized it, is where the damage happens.
Why this is especially rough if you are not an engineer
There is no error log to open. There is no red screen telling you what broke. The work just quietly stops moving, and you have no way to know if it is a temporary hiccup, something you did, or a real problem on the tool’s side. So you wait, or you start second-guessing your own setup, or you find out the hard way when someone complains. A 19-minute disruption sounds short, but if it lands at the wrong moment, it is long enough to miss a deadline or leave a customer waiting with no explanation.
Timeline
- 21:40 UTC, July 24, 2026: Bolt.new reports a bigger problem.
- About 19 minutes of disruption.
- 22:00 UTC, July 24, 2026: Bolt.new marks 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 check anything yourself. That turns “my customer just told me something is broken” into “I got a heads-up within a minute of Bolt.new’s own report, and I already knew.”
It also watches the things you ship. If you have n8n workflows, NoCrash 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 side, that surfaces too, in the same place.
To be clear about what this is: NoCrash reads what Bolt.new publishes publicly and tells you fast. It does not find the outage before Bolt.new’s own status page does. But it means you are not the last to know.
For the authoritative account of this disruption, see Bolt.new’s official status page at https://status.bolt.new/proxy/status.bolt.new.