On the evening of July 16, 2026, Bolt.new had a significant problem starting at 18:35 UTC. It lasted about three hours and was resolved at 22:06 UTC. Bolt.new has since reported the issue as resolved.
Who this hits and how they usually find out
If you build or run something on Bolt.new, an outage like this does not announce itself to you. There is no email, no pop-up, no alert. Your project just stops working, quietly, while you are doing something else. The shape of it is almost always the same: a customer tries to use what you built, hits a wall, and sends you a message. That message is how you find out. By then the problem has already been going on for a while, and the customer is already frustrated.
Why this is especially rough without a technical background
If you are not an engineer, there is nothing to look at when something goes quiet. No log file, no error on your screen, no red light anywhere you can see. The work just stops moving. Your automations sit still, your app does nothing, and from your side everything looks fine. The first real signal is an unhappy person on the other end. That gap, between when the tool broke and when you heard about it, is the part that costs you.
Timeline
- 18:35 UTC - Bolt.new started experiencing a bigger problem.
- About 3 hours - the disruption continued with no recovery.
- 22:06 UTC - Bolt.new reported the issue resolved.
How a watcher catches this before your users do
NoCrash reads Bolt.new’s own public status page once every minute. The moment that page flips from working to having trouble, NoCrash sends you a plain-language message telling you what broke and when. You do not have to go looking for it, and you do not have to wait for a customer to tell you. You find out in plain English, within a minute of Bolt.new’s own report, sitting next to everything else you build on.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those too. If you have an app, you can give NoCrash a URL or drop in a small JS snippet, and it will watch that as well. So if something goes quiet on your own side, that surfaces the same way.
What it does not do: it does not find the outage before Bolt.new’s own status page does. It reads what Bolt.new publishes, as fast as it publishes it, and tells you in words you can act on.
For the authoritative account of this outage, see Bolt.new’s own status page at https://status.bolt.new/proxy/status.bolt.new.