Bolt.new had a significant outage on July 28, 2026, starting just after 04:00 UTC and lasting roughly three hours. The service reported a bigger problem and later confirmed it resolved around 08:01 UTC. No detailed cause has been published.
Who this kind of outage hits
If you build or ship something on Bolt.new, you probably found out about this the worst possible way: a customer messaged you, or you woke up to something broken. That is the normal shape of a quiet platform outage. The tool does not call you. Your app or workflow just stops doing what it was supposed to do, and the first person to notice is usually someone who paid you money. By the time you hear about it, the problem may have been running for an hour or two already.
Why it is especially rough if you are not an engineer
There is nothing to read. No error on your screen, no log file, no alert. The work just stops moving. If you have an automation that sends a welcome email, processes a form, or builds something for a user, it silently queues up or fails with no signal to you at all. You find out when a customer asks why their thing never arrived, or why the app looks broken. At that point you are already behind, already apologizing, already trying to explain something you did not know was happening.
Timeline
- 04:04 UTC, July 28, 2026 - Bolt.new reports a bigger problem on its public status page.
- Roughly 3 hours - the disruption runs while builds, workflows, or anything depending on Bolt.new may have been affected.
- 08:01 UTC, July 28, 2026 - Bolt.new reports 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. You find out within a minute of Bolt.new’s own report, not an hour later when a customer complains.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those too. If you give it a URL or drop in a small JS snippet for your app, it watches that side as well. So if something goes quiet on your own end, that surfaces alongside anything happening at the platform level. Everything sits in one place, in plain English.
To be straight about what this is: NoCrash reads what Bolt.new publicly reports. It does not find the outage before Bolt.new does. It just makes sure you hear about it right away, in plain language, instead of finding out from a frustrated user.
For the authoritative account of this outage, see Bolt.new’s own status page at https://status.bolt.new/proxy/status.bolt.new.