Bolt.new had a bigger problem starting August 3, 2026 at around 14:25 UTC. It lasted about two days, recovering on August 5 at 18:01 UTC. Bolt.new has since reported the issue resolved.
Who this kind of outage hits
If you build on Bolt.new, you are probably not watching its status page. Most people are not. So when something goes wrong, the first signal is usually a customer writing in to say something is broken, or a collaborator asking why a project link stopped loading. That gap, between when the tool stopped working and when you found out, can be hours. Sometimes it is a full day. The shape is always the same: you were the last to know.
Why it is especially rough without a technical background
When a tool like Bolt.new goes quiet, there is no error message waiting for you. Nothing in your inbox says “this broke at 2pm.” Your work just stops moving. A project that should have been ready is not ready. A client who expected something is now waiting. You start second-guessing yourself, wondering if you did something wrong, before you even think to check whether the tool itself is the problem. By the time you find the status page and confirm it was not your fault, the customer is already frustrated.
Timeline
- August 3, 2026, 14:25 UTC: Bolt.new began experiencing a bigger problem.
- About 2 days of disruption followed.
- August 5, 2026, 18:01 UTC: Bolt.new recovered and reported the issue resolved.
How a watcher catches this before your users do
Bolt.new has a public status page. It updates when something goes wrong. The problem is that nobody is sitting there refreshing it every minute, and nothing pings you when it changes.
NoCrash reads that public status page every minute. The moment Bolt.new’s own page flips from working to having trouble, NoCrash sends you a plain-language message saying what changed and roughly how bad it looks. You find out within a minute of Bolt.new’s own report, in words you can act on, not in status jargon you have to decode. That is the difference between “my customer told me two hours in” and “I got a calm heads-up and could tell my client something before they had to ask.”
NoCrash also watches the things you ship. If you have n8n workflows running, it watches those too. If you give it a URL for your app, it keeps an eye on that. So a quiet stall on your own side surfaces the same way, in one place, in plain English.
To be clear about what it does not do: NoCrash reads public status pages and watches what you point it at. It does not find outages before the tool’s own status page does.
For the authoritative account of this outage, see Bolt.new’s official status page at https://status.bolt.new/proxy/status.bolt.new.