Bolt.new site stopped working: hosting limits and other causes
A Bolt.new site that suddenly stops loading mid-month has often hit its hosting allowance: Bolt's help center says Free sites go offline until usage resets at the next billing cycle, and Pro sites pause when they reach the spending cap you set. Limits are shared by every site on the account. If you are within limits, check status.bolt.new for an incident, and test from mobile data in case a network is blocking .bolt.host.
What you'll see
The site loaded fine for weeks, then visitors report it is down, or it fails only for some of them. You did not publish anything new. Some people see ERR_SSL_PROTOCOL_ERROR or a connection error on one network while it works on another.
Why it happens
1. Free plan hosting allowance used up
Bolt's plans page lists the Free allowance as 10 GB of bandwidth and 333,333 requests a month (as of October 2026), with a hard stop. When it is reached, the site stays offline until the next billing cycle.
2. Pro spending cap reached
Pro includes a larger allowance and pay-as-you-go beyond it, up to a cap you choose. Bolt says once the cap is reached, the site pauses until usage resets.
3. Another site on the account used the allowance
Limits are account-wide. A demo with a large video, or a project that suddenly got traffic, can take a quiet business site offline with it.
4. A network block or a platform incident
Some school, office or country filters block .bolt.host addresses, which shows as an SSL protocol error. A Bolt outage looks similar, so check status.bolt.new before changing anything.
How to fix it
- Check status.bolt.new for an active hosting incident first; if there is one, wait for it to clear.
- Open the site on your phone over mobile data. If it works there but not on a particular Wi-Fi network, that network is blocking .bolt.host and a custom domain is the long-term fix.
- Review hosting usage for your account and plan, and confirm the current limits on Bolt's hosting plans page, since numbers change. Bolt's docs do not say where usage is shown, so contact support if you cannot find it.
- On Pro, raise the cap at profile icon > Settings > Cloud > Change spending limit. On Free, upgrading is the only way to bring a site back before the reset.
- Unpublish demos and old experiments you no longer need so they stop using the shared allowance.
- Cut page weight: compress images, serve them at display size, and host large video on a video platform rather than in the project.
Prompt to paste into Bolt.new
Reduce this site's bandwidth: convert images to WebP, resize them to the size they are displayed at, lazy-load images and videos below the fold, and replace any self-hosted video files with an embed from an external video host. Do not change the design.
How to check it's fixed
- Load the site from two different networks, such as home Wi-Fi and mobile data.
- Set up a free uptime monitor on the homepage so you hear about the next outage before customers do.
What a QAlaunch scan shows for this
- The site failing to load, or returning an error page, when the scan visits it.
- A low PageSpeed performance score and heavy images, which use up hosting bandwidth fastest.
- It cannot see your Bolt usage or billing, only whether visitors currently get the site.
See exactly what a full report contains in the sample report.
Frequently asked questions
What do visitors see when a Bolt site hits its limit?
Bolt's help center says the site stops displaying publicly but does not describe the exact page visitors get. Treat any sudden mid-month outage as a reason to check usage.
Do limits apply per site or per account?
Per account. All published sites share the same monthly bandwidth and request allowance, so one busy project affects the others.
How do I stop it happening again?
Keep business sites on a paid plan with a sensible spending cap, remove unused projects, keep images light, and run an uptime monitor so you know within minutes rather than days.
Rather have a QA engineer test it by hand?
If this is a site you're launching or handing to a client, I'll go through it by hand, including the Bolt.new-specific issues a scan can't reach, like logged-in flows.
- Up to 10 key pages tested by hand, not a scan
- Every flow a customer uses: forms, sign-up, checkout, booking
- Real mobile and desktop browsers
- A written report in plain language, with screenshots
- A 15-minute call to walk you through it
- 10 years of professional QA experience
Tell me about your site and I'll reply personally, usually the same day.
No payment now. I'll confirm scope and price first.
Related fixes
- Bolt.new custom domain not connecting: causes and fixes
- Bolt.new blank page after deploy: causes and fixes
- Bolt.new site shows 404 on refresh: the Netlify fix
- Bolt.new environment variables not working after deploy
- Bolt.new Google sign-in not working: causes and fixes
- Bolt.new emails not sending: contact forms and auth emails
More for Bolt.new: all Bolt.new fixes · Bolt.new testing · 9 bugs every AI-built site ships with
Written by Waqas Ahmad, QA engineer with 10 years of professional testing experience. Last checked October 26, 2026.
Sources: Bolt help center: hosting plans · Bolt help center: troubleshoot hosting