On July 16, 2026, Bolt.new had a significant disruption starting at 16:57 UTC. It lasted about an hour and was resolved by 18:17 UTC. Bolt.new has since confirmed the issue is resolved.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, an outage like this does not announce itself to you. Your app stops doing what it should, your automations go quiet, and nothing sends you a message. The first signal is usually a customer writing in to ask why something is broken. By then the damage is already done: the customer has lost trust, you are scrambling to explain something you only just learned about yourself, and the outage may already be over. That gap between “it broke” and “I found out” is the expensive part.
Why this is especially rough if you are not an engineer
There are no logs to read. There is no error on your screen. The work just stops moving. If you have an n8n workflow that runs every hour, it may have queued up silently with no warning. If your app depends on Bolt.new for something customer-facing, your users hit a wall and you had no idea. A non-engineer operator has no obvious place to look, so the first real signal is an unhappy person on the other end. That is a hard way to find out your tools are down.
Timeline
- 16:57 UTC, July 16, 2026: Bolt.new’s public status page reported a bigger problem.
- About 1 hour: The disruption lasted roughly 60 minutes.
- 18:17 UTC, July 16, 2026: Bolt.new marked 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 one place, alongside everything else you build on. You do not have to check anything. You do not have to wait for a customer to write in. You find out within a minute of Bolt.new’s own report, in words you can act on immediately.
NoCrash also watches the things you ship. If you have n8n workflows, it watches those through your API token. If you have an app, it watches it through a URL you give it or a small JS snippet you drop in. So if something goes quiet on your own side, that surfaces too, separately from what the tool’s status page says.
None of this means NoCrash finds the problem before Bolt.new does. It reads Bolt.new’s own public report and tells you about it fast, in plain English, without you having to go looking. The difference between “my customer told me” and “I got a calm heads-up first” is just whether someone was watching.
For the authoritative account of this outage, see Bolt.new’s official status page at https://status.bolt.new/proxy/status.bolt.new.