What happened
Bolt.new had a significant disruption starting at 00:04 UTC on August 13, 2026. It lasted roughly two hours and recovered at 03:01 UTC. Bolt.new has since reported the issue resolved. No detailed cause has been published beyond that.
Who this hits and how they usually find out
If you build on Bolt.new, your projects, your automations, anything that depends on it being available, just stops working when it goes down. You probably do not find out from a log or an alert. You find out because a customer emails you asking why something is broken, or because you happen to open the tool yourself and notice it is not responding. That gap, between when the tool stopped working and when you found out, is where the damage happens. A customer already had a bad experience before you even knew there was a problem.
Why this is especially rough without a technical background
If you are not an engineer, there is no error screen to read, no log file to check. The work just stops moving. A workflow that should have run at 1 AM did not run. An app that should have responded did not respond. Nothing tells you. The first signal is usually an unhappy customer or a missed deadline, and by then you are already behind. You are not debugging a system, you are apologizing to someone.
Timeline
- 00:04 UTC, August 13, 2026 - Bolt.new’s own status page reported a bigger problem.
- ~02:57 of disruption - The tool was unavailable or significantly degraded.
- 03:01 UTC, August 13, 2026 - 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. Not a status code, not a raw alert. Something like “Bolt.new is reporting a bigger problem right now.” That happens within a minute of Bolt.new’s own report, which means you know before you hear it from a customer.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those through an API token. If you have an app, you can give NoCrash a URL or drop in a small JS snippet, and it watches that too. So if something goes quiet on your own side, that surfaces as well, sitting next to everything else in one place.
What it does not do is find the outage before Bolt.new’s own status page does. It reads what Bolt.new publishes, as fast as possible, and tells you in plain English. That is the whole thing.
For the authoritative account of this outage, see Bolt.new’s official status page: https://status.bolt.new/proxy/status.bolt.new