Cancelling a VPS is a 14-item audit, not a button. The machine takes one click; the eleven things attached to it take between two hours and two weeks to unwind. DNS TTLs, TLS reissuance, SPF records, outbound IP reputation, partner allow-lists, cron secrets and monitoring probes all outlive the server they point at. Miss the wrong one and you pay for the exit twice: once on the old invoice while it runs out its notice period, and again in downtime, reissued certificates, or a payment processor refusing orders from an IP nobody whitelisted.<\/p>\n\n
The checklist below is ordered by lead time, longest first. It assumes a typical budget VPS running a site or two, mail for one domain, and a handful of scheduled jobs. Public-internet items come first because DNS propagation and certificate issuance cannot be accelerated by working longer hours.<\/p>\n\n
Two schedules run during an exit. The first is your DNS TTL: a record with a 3600-second TTL stays cached for an hour after you change it, and some ISP resolvers hold it longer. Drop every relevant TTL to 300 seconds at least 48 hours before cutover so the switch window collapses to five minutes. The second is the provider’s notice period — commonly 7 to 30 days, sometimes “end of current billing term” — plus the retention period before the old disk is destroyed, which ranges from immediately to 7 days.<\/p>\n\n