---
title: "Recently restocked VPS plans — verified restocks, not rumors"
description: "VPS plans that flipped from out of stock or low stock to in stock in the last 90 days, each backed by two consecutive verified stock readings. No restock is claimed without the observation pair."
canonical: https://vpsledger.com/recently-restocked/
verified: 2026-09-12
format: text/markdown
html: https://vpsledger.com/recently-restocked/
---

> Markdown alternate of <https://vpsledger.com/recently-restocked/>. Generated at build time from the
> same dataset as the HTML page; prices verified 2026-09-12. Data is a build-time
> snapshot — no live API, no auth. Machine entry point: <https://vpsledger.com/ai/>.

# Recently restocked VPS plans

No verified restocks in the last 90 days yet — 3 are needed before this page has anything worth indexing.

## Why this page is empty (and stays up anyway)

1. A stock check of a provider's official page appends one reading to the append-only stock log.
2. When a plan's new reading follows an out-of-stock or low-stock reading, that transition is a restock event.
3. This page lists every restock in the last 90 days — newest first, each citing both readings.

Today the seed carries exactly one stock reading per plan (183 readings across 183 plans), and a single reading is a state, not a history. A restock claim needs the sell-out AND the come-back — anything else would be invented. The page exists so the data has a home the moment the first transition lands.

Until then: [plans in stock now](/in-stock/) · [stock changes](/changes/) · [providers](/providers/).