Skip to main content
Bolt.new logo

Is Bolt.new Down?

No — Bolt.new is up

Reachable from all 8 checked regions

Average response time: 856ms

Last checked · checks run every 6 hours

Official status page: https://status.bolt.new

Bolt.new uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
560ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 20 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

20-day clean streak
Sep 14: no data
Sep 15: no data
Sep 16: no data
Sep 17: no data
Sep 18: no data
Sep 19: no data
Sep 20: no data
Sep 21: no data
Sep 22: no data
Sep 23: no data
Sep 24: 100.00% uptime, 16 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 30 checks
Oct 1: 100.00% uptime, 32 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
938ms
DNS 195ms TCP 2ms TLS 10ms TTFB 806ms
arn
783ms
DNS 189ms TCP 1ms TLS 7ms TTFB 634ms
nrt
1951ms
DNS 185ms TCP 1ms TLS 8ms TTFB 1853ms
ord
638ms
DNS 38ms TCP 23ms TLS 29ms TTFB 590ms
sin
888ms
DNS 82ms TCP 1ms TLS 8ms TTFB 673ms
sjc
452ms
DNS 104ms TCP 2ms TLS 12ms TTFB 445ms
syd
774ms
DNS 130ms TCP 1ms TLS 6ms TTFB 581ms
yyz
427ms
DNS 82ms TCP 1ms TLS 9ms TTFB 424ms

What Bolt.new does

Bolt.new is an AI app builder made by StackBlitz. You describe a website or app in a chat, Bolt writes the code, runs a live preview inside your browser and publishes the result to a free bolt.host address or, on paid plans, a custom domain. Because the building happens through prompts, a Prompting incident stops most work even when bolt.new itself still loads.

What an outage looks like

Prompts hang, stop partway through a build, or return an error in the chat with an error ID at the bottom of the message. Projects fail to save. The Publish menu cannot push an update to your live site. GitHub sync fails while GitHub has its own incident. A blank or stuck preview is more often local, because the preview runs in your own browser.

What to do about it

Check status.bolt.new, which lists bolt.new, Prompting and Publishing separately and posts dependency checks when GitHub, Cloudflare or Anthropic report outages. Avoid resending the same large prompt over and over: Bolt consumes tokens when it reads and builds your project. Small fixes can be made by hand in Code view, which uses no tokens. Paid users can email support@bolt.new with the error ID; free users get help on Discord.

Is it down for everyone, or just you?

If this page says Bolt.new is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

L
Lovable
GitHub
GitHub
Supabase
Supabase
Cloudflare
Cloudflare

Bolt.new outage FAQ

Is Bolt.new down or is it my browser?
Check which part is failing. The preview runs in your own browser on StackBlitz's WebContainers runtime and uses your device's resources, so a blank or stuck preview is often local. Bolt's troubleshooting guide suggests a hard refresh, disabling ad blockers and VPNs, and using Chrome or another Chromium-based browser. If prompts fail too and the Prompting row on status.bolt.new is degraded, the problem is Bolt.
Is status.bolt.com the status page for Bolt.new?
No. status.bolt.com belongs to a different product called Bolt and lists components such as Checkout, Payment Processing and e-commerce plugins. The status page for the StackBlitz AI builder is status.bolt.new. Search results mix the two, so check the domain before trusting a green or red verdict about your Bolt.new projects.
Why is my published Bolt site not loading?
It may have hit its hosting limit rather than being caught in an outage. Sites on Bolt hosting stop displaying publicly when they reach their plan's hosting limits and come back when usage resets at the start of the billing cycle; paid plans can raise the spending limit. If limits are fine, check the Publishing row on status.bolt.new. Republish with the Publish or Update button, since asking Bolt to publish in chat uses tokens.
Does a GitHub or Anthropic outage affect Bolt.new?
It can, and Bolt tracks it. Its incident history includes dependency-check notices posted when GitHub, Cloudflare, Anthropic and Name.com reported outages, so check the upstream provider's own status page too. If GitHub is the problem, code already pushed to a connected repository is still there, and Bolt's own version history is a separate record of your project.
Will I lose my project during a Bolt outage?
Bolt keeps earlier versions of a project in several places. Its version history, opened with the View history button, lets you preview and restore saved versions, and a connected GitHub repository holds a full history outside Bolt. A prompt that failed mid-build can leave code half changed, so after recovery check the latest version and restore an earlier one if needed.

How we measure this

  • We request Bolt.new's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Bolt.new publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Bolt.new goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required