On July 21, 2026, Bolt.new reported a bigger problem starting at 17:45 UTC. It lasted about 19 minutes and was marked resolved at 18:05 UTC. Bolt.new’s own status page now shows the disruption is over.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, a short outage like this can stop your work cold with no warning inside the tool itself. You might be mid-build, or a workflow you set up might be running quietly in the background. The first sign something went wrong is often a customer message, a missed delivery, or a confused reply asking why nothing came through. By then the disruption is already over, but the damage to trust is done. That gap, between when the tool stopped and when you found out, is the part that stings.
Why this is especially rough if you are not an engineer
There are no logs to check. There is no error on your screen. The work just stops moving, and you have no way to know if it is your setup, your account, or the tool itself. You start second-guessing your own configuration. You might spend twenty minutes poking at settings before someone mentions they saw a status update. A non-engineer operator has no fast path to “it is them, not me,” and that uncertainty is its own kind of cost.
What the timeline looked like
- 17:45 UTC - Bolt.new reports a bigger problem begins.
- 18:05 UTC - Bolt.new marks the disruption resolved.
- Total duration - about 19 minutes.
The disruption was short. But 19 minutes is long enough for queued runs to pile up, for a customer to notice something missing, and for you to spend real time wondering what broke.
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. You find out within a minute of Bolt.new’s own report, not an hour later from a frustrated customer.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those through your API token. If you have an app, you can give it a URL or drop in a small JS snippet and it will watch that too. So if something goes quiet on your own side, that surfaces as well, sitting next to everything else you build on.
NoCrash does not find outages before the tool’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 disruption, see Bolt.new’s official status page at https://status.bolt.new/proxy/status.bolt.new.