What actually caused this?

Bolt.new has not published a detailed cause for this disruption. The status note confirms it has been resolved. For any further detail, check the official status page at https://status.bolt.new/proxy/status.bolt.new.

Could this happen again?

Yes. Any tool can have another outage. That is not a knock on Bolt.new specifically, it is just true of every service. The question is not whether it will happen again, it is whether you will hear about it before your users do.

I only use Bolt.new occasionally. Do I still need to worry?

Even occasional use means customers or collaborators may be depending on something you built there. A 28-minute disruption during a busy afternoon is enough to break a demo, stall a handoff, or confuse a client. The less you are watching, the more a quiet outage costs you.

How do I find out faster next time something like this breaks?

NoCrash reads Bolt.new's public status page every minute and sends you a plain-language heads-up within a minute of Bolt.new's own report. You do not have to check anything yourself. The message comes to you, in plain English, before the first confused customer message lands in your inbox.

Bolt.new outage on June 25, 2026: what happened and what to watch for

On June 25, 2026, Bolt.new reported a bigger problem starting at 14:04 UTC. It lasted about 28 minutes and was marked resolved at 14:33 UTC. Bolt.new has since confirmed the disruption is over. The cause has not been published in detail.

Who this kind of outage hits

If you build on Bolt.new, you probably are not sitting there watching its status page. You are building something, or you are away from your computer entirely. When the tool goes quiet, nothing inside it sends you a message. No alert, no email, no red banner. The first signal most people get is a customer writing in to say something is broken, or a collaborator asking why their project stopped loading. By then the outage may already be over, but the damage to trust is done.

Why it is especially rough without a technical background

If you are not an engineer, there is no log file to open, no error trace to read. The work just stops. A build does not finish. A prompt does not respond. You refresh the page, maybe try a different browser, maybe blame your internet connection. The quiet is the problem, and quiet does not tell you anything useful. The first real signal is still an unhappy person on the other end.

What the timeline looked like

14:04 UTC - Bolt.new reported a bigger problem was underway.
14:33 UTC - Bolt.new marked the disruption resolved.
Total duration - about 28 minutes.

That is a short window, but 28 minutes is long enough for a customer to notice, for a workflow to stall, and for trust to take a small hit you did not see coming.

How a watcher catches this before your users do

NoCrash reads Bolt.new’s public status page once every minute. The moment that page flips from working to having trouble, NoCrash sends you a plain-language message. Not a status code, not a raw feed entry. A sentence you can read and act on, sitting next to everything else you build on.

It also watches the things you ship. If you have n8n workflows running, NoCrash watches those too. If you give it a URL or drop a small JS snippet into your app, it watches that as well. So a quiet stall on your own side surfaces the same way, in the same place.

To be straight about what this means: NoCrash does not find the outage before Bolt.new’s own status page does. It reads that page and tells you within a minute of Bolt.new’s own report. The difference is that you hear it in plain English, immediately, rather than from a customer an hour later.

The authoritative account

For the official record of this disruption, go to Bolt.new’s own status page: https://status.bolt.new/proxy/status.bolt.new