On July 24, 2026, Bolt.new had a significant problem starting at 14:15 UTC. It lasted about three hours and was resolved at 17:18 UTC. Bolt.new has since reported the issue as resolved.
Who this kind of outage hits
If you build on Bolt.new, you are probably not watching its status page while you work. You are building, or you are away from your desk, or you are handling something else entirely. When the tool goes quiet, nothing inside it sends you a message. No alert, no email, no red banner. The first signal is usually a customer writing in to say something is broken, or a collaborator asking why nothing is working. By then the outage has already been running for a while and you are already behind.
Why it is especially rough without a technical background
When you have no logs to read and no error on the screen, a quiet outage looks identical to a slow afternoon. Work stops moving. Builds do not finish. You refresh, you wait, you wonder if it is your connection. There is no obvious moment where you know something is wrong. The first hard signal is an unhappy person on the other end, and by then you are explaining a problem you did not even know existed. That gap, between when the tool broke and when you found out, is the part that costs you.
What happened and when
- 14:15 UTC, July 24, 2026: Bolt.new began experiencing a bigger problem.
- For about 3 hours: The disruption continued. Bolt.new’s own status page reflected the issue during this window.
- 17:18 UTC, July 24, 2026: Bolt.new resolved the issue and reported it as fixed.
Bolt.new has not published a detailed explanation of the cause beyond confirming the issue is 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 plain English, telling you what is wrong. Not a status code. Not a raw feed. A sentence you can read and act on immediately.
That means instead of hearing about a three-hour outage from a frustrated customer, you hear about it within a minute of Bolt.new’s own public report. You can post a quick note to your users, pause a campaign, or just know to stop troubleshooting your own setup. The disruption is the same length either way. The difference is whether you are ahead of it or behind it.
NoCrash also watches the things you ship. If you have n8n workflows running, it watches those too. If you give it a URL or add a small JS snippet to your app, it watches that as well. So if something goes quiet on your own side, that surfaces in the same place, alongside everything else you build on.
For the authoritative account of this outage, see Bolt.new’s official status page at https://status.bolt.new/proxy/status.bolt.new.