On August 10, 2026, Bolt.new had a significant disruption starting at 09:13 UTC. It lasted about three hours and was resolved at 12:20 UTC. Bolt.new has since reported the issue as resolved.
Who this kind of outage hits
If you build or run something on Bolt.new, a three-hour window where the tool is having a bigger problem means your app, your automations, or your builds may have stalled without a single alert reaching you. Most people find out the wrong way: a customer writes in to say something is broken, or they notice a job never finished, and only then do they go looking. By that point the damage is already done, the customer is already frustrated, and you are already behind.
That gap, between when the tool stopped working and when you found out, is the part that costs you.
Why this is especially rough without a technical background
If you are not an engineer, there is no log file to open, no error message on a screen. The work just quietly stops. A workflow that should have run at 09:30 simply did not run. An app that should have responded went quiet. Nothing told you. The first signal is often a confused or unhappy user, and by then you are explaining a problem you did not even know existed an hour ago. That is a hard position to be in, and it is the normal experience for most solo operators and small teams.
What the timeline looked like
- 09:13 UTC - Bolt.new’s own status page reported a bigger problem.
- 09:13 to 12:20 UTC - The disruption continued for about three hours.
- 12:20 UTC - Bolt.new reported 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 does not mean NoCrash finds the problem before Bolt.new does. It means you hear about it within a minute of Bolt.new’s own report, instead of an hour later when a customer tells you.
On top of that, NoCrash watches the things you ship. It watches your n8n workflows through an API token, and it watches 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.
The result is that “my customer told me” becomes “I got a calm heads-up first, and I had time to post a note before anyone asked.”
For the authoritative account of this outage, see Bolt.new’s official status page at https://status.bolt.new/proxy/status.bolt.new.