Short answer: When a provider changes a VPS range, "the same configuration" stops being one thing. On 2026-11-18 OVHcloud told existing customers they may need a different model to buy today's specs, DigitalOcean limits resize to the same plan family, Hetzner keeps deprecated CX and CCX generations on paper but no longer sells them, and Vultr treats a server-type change as a snapshot-and-new-server migration. The four official pages use four different nouns for one idea: a spec row is not a portable object.
Every cell comes from an official provider page opened on 2026-11-18. Where the page printed no statement, the cell says so and names the pages read.
| Provider | Range or plan statement as printed | What "same configuration" means here | Route printed for an existing customer | Data / IP / reboot on that route | Official source (opened 2026-11-18) |
|---|---|---|---|---|---|
| OVHcloud (US) | "VPS 2027 Range: More Resources, More Security"; four starting prices printed as $4.54, $8.50, $12.32 and $23.37 per month [S1] | "To purchase the same configuration you have today, you may need to choose a different model"; "the configurations for the other models have shifted" [S1] | One-click upgrade "without changing servers"; downgrade requires a new plan, a data transfer and cancellation of the old service [S1] | Upgrade needs "just a quick reboot" and "no data migration or configuration changes needed"; IP behaviour on either route: Read not available on the page read [S1] | us.ovhcloud.com/vps/ [S1] |
| DigitalOcean | Resize is split by configuration family: "Droplets created with a v5 configuration resize only to other v5 configurations, and Droplets created with a bundled plan resize only to other bundled plans" [S2] | A configuration is a family boundary, not a list of vCPU and RAM numbers; cross-family resize is not offered on the page read [S2] | Resize inside the same family; target plan must have "equal or greater amount of disk space as the original Droplet" [S2] | Power off before resize; API powers down automatically; "Droplets may change hypervisors during a resize"; IP behaviour: Read not available on the page read [S2] | docs.digitalocean.com/products/droplets/how-to/resize/ [S2] |
| Hetzner | "Below is a list of old server plans that are deprecated and no longer available for order"; CX Gen1 1 vCPU / 1 GB / 25 GB through CX Gen2 16 vCPU / 32 GB / 320 GB and CCX Gen1/Gen2 rows remain printed [S3] | An old configuration remains an exact published row, but the deprecated CX and CCX generations cannot be ordered again [S3] | Rescale in Console to a current plan, up or down, inside the same architecture; when scaling up, keep the current disk size to preserve a later downgrade [S4] | CPU type may change on rescale because hardware is allocated by availability; disk cannot be shrunk; partition must be enlarged via Rescue System; rescale reboot and IP retention: Read not available on the pages read [S3][S4] | docs.hetzner.com/cloud/servers/deprecated-plans/ [S3]; docs.hetzner.com/cloud/servers/faq/ [S4] |
| Vultr | The upgrade guide distinguishes an in-place plan change from a "server migration" when "changing server types, such as moving from Cloud Compute to Optimized Cloud Compute" [S5] | A configuration is tied to the server type; changing type is not the same action as changing plan inside a type [S5] | In-place Change Plan when the host has capacity; otherwise take a snapshot and deploy a new server from it [S5] | In-place upgrade restarts the server and keeps the IP; the snapshot migration gives the new server "a new IP address" [S5] | docs.vultr.com/how-to-upgrade-your-plan-without-reinstalling [S5] |
Four official pages, four meanings of configuration: a model that may have to change, a resize family, a deprecated spec row, and a server type. A price list that shows only vCPU, RAM and disk hides all four.
community.enhance.com): a control-panel migration thread for one platform; no provider range notes or side-by-side config rules. This page supplies four official statements.github.com/ovh/infrastructure-roadmap): an issue tracker request, not a published provider policy or price. This page quotes only provider pages.community.ovhcloud.com): a customer discussion in French about the new range; not an official statement of what existing customers must do. This page uses OVHcloud's own product page note.help.softsyshosting.com): a single hosting provider's article about its own plans. This page compares four providers' own documentation.blog.netwisp.com): a 2016 post about features, not about a 2027 range or existing-customer configurations. This page uses 2026-11-18 pages only.community.ovhcloud.com): a performance complaint thread, with no official range note or reproducible figures. This page prints no unsourced performance claim.An existing page on this site, VPS upgrade downgrade paths, records the official plan-change facts for DigitalOcean, Vultr and Hetzner: the resize family, the server-type migration and the rescale disk floor. OVHcloud's official page read today adds a fourth kind of change: its note to existing customers says the same configuration may now require a different model. The site's existing facts and today's OVHcloud note are both official; placed together, they show that "same configuration" is not a single promise across providers.
When the old model can no longer be ordered, the question becomes what can be undone after a move; VPS downgrade rollback follows the disk floor, the data copy and the address rules that decide whether the return trip is possible.
OVHcloud's 2027 range page says daily automatic data backups and one-click upgrades are part of the new range, and prints four monthly starting prices without tying them to the configurations an existing customer owns today. [S1]
DigitalOcean's resize guide separates a CPU/RAM-only resize from one that also enlarges the disk permanently, and recommends a snapshot before either operation. [S2]
Hetzner's deprecated-plans page keeps the full CX and CCX rows online after removing them from ordering, including 1 vCPU / 1 GB / 25 GB for CX10 Ceph and 48 vCPUs / 192 GB / 960 GB for CCX62 Gen2. [S3] Its FAQ restricts rescale to the same architecture and says CPU type may change. [S4]
Vultr's guide says an in-place upgrade needs spare host capacity and gives a snapshot-based migration route when it is absent; the two routes have different IP outcomes. [S5]