Bolt.new had a significant disruption on the morning of June 26, 2026. It started at 07:00 UTC and was resolved by 08:00 UTC, lasting about 59 minutes. Bolt.new has since reported the issue resolved, with no detailed cause published at this time.
Who this kind of outage hits, and how they usually find out
If you build on Bolt.new, a disruption like this hits you quietly. Your app stops responding, your builds stall, your automations go nowhere. But nothing sends you a message. The first sign is often a customer writing in to say something is broken, or a colleague asking why a workflow never finished. By then the outage may already be over, but the damage to trust is done. That gap between “it broke” and “you found out” is the part that costs you.
Why this is especially rough without a technical background
If you are not an engineer, there is no log file to open, no error screen to read. The work just stops moving. A form submission goes nowhere. A workflow sits frozen. You might spend twenty minutes checking your own setup, wondering if you broke something, before it even occurs to you to check whether the tool itself is having trouble. That lost time, and the anxiety that comes with it, is the real cost of a quiet outage.
Timeline
- 07:00 UTC, June 26, 2026: Bolt.new began experiencing a bigger problem.
- 07:00 to 08:00 UTC: The disruption continued for about 59 minutes.
- 08:00 UTC: Bolt.new reported 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 words you can act on, without you having to go check anything yourself. That turns “my customer told me an hour later” into “I got a calm heads-up within a minute of Bolt.new’s own report.” It also watches the things you ship: your n8n workflows through an API token, and your app through a URL or a small JS snippet you add. So if something goes quiet on your own side, that surfaces too, all in one place. NoCrash does not find the outage before Bolt.new’s own status page does. It reads that page and tells you fast, in plain English, the moment the tool itself reports trouble.
For the authoritative account of this outage, see Bolt.new’s official status page at https://status.bolt.new/proxy/status.bolt.new.