On the evening of June 22, 2026, Bolt.new reported a bigger problem starting at 19:20 UTC. It lasted about two minutes and was resolved by 19:22 UTC. Bolt.new has since marked it resolved, with no detailed cause published at this time.
When something breaks quietly, you usually hear about it from a customer first
Most people who build on Bolt.new are not watching its status page. Why would they be? They’re building, shipping, answering emails. So when something goes wrong, the first signal is often a customer message: “hey, this isn’t working.” By that point the disruption may already be over, but the damage to trust is done. You’re left explaining something you didn’t even know had happened.
That pattern, finding out from a user instead of from a system, is the default for most solo operators and small teams. It’s not a personal failure. It’s just how these tools work unless you set something up to watch them.
Why this is especially rough if you’re not an engineer
There’s no error log to open. No red screen. The work just stops moving and you have no idea why. Is it your code? Your workflow? The tool itself? You start poking around, wasting time on the wrong thing, while a customer is already frustrated. A two-minute disruption like this one is short enough that you might not even catch it yourself. But if a customer hit it at exactly the wrong moment, it felt much longer to them.
That gap between “something is wrong” and “I know what is wrong” is where trust quietly erodes.
What the timeline looked like
- 19:20 UTC, June 22, 2026 - Bolt.new reports a bigger problem begins
- 19:22 UTC, June 22, 2026 - Bolt.new reports the issue is resolved
- Total duration - about 2 minutes
Short, but real.
How a watcher catches this before your users do
Bolt.new publishes a public status page. NoCrash reads that page every minute. The moment it flips from working to having trouble, NoCrash sends you a plain-language message, in words you can act on, without you having to go look. For a two-minute disruption like this one, that means you could know within a minute of Bolt.new’s own report, rather than finding out from a customer later.
NoCrash also watches the things you ship: your n8n workflows through an API token, and your app through a URL you give it or a small JS snippet. So if something goes quiet on your own side, that surfaces too, sitting next to everything else you build on. It does not claim to find problems before the tool’s own status page does. It just makes sure you don’t miss what the status page is already saying.
For the authoritative account of this disruption, see Bolt.new’s official status page: https://status.bolt.new/proxy/status.bolt.new