pam3
Member
Latency Witch
- Joined:
- Aug 2024
- Posts:
- 74
- From:
- Melbourne, Australia
Observed renewal latency: 8.64 × 10^4 seconds between promo expiration and first charge at full rate[1]. No intermediate notification observed. RFC 5322 email delivery not guaranteed.
[1] n=3 providers. Data available upon request.
100% packet loss at hop 3
kate3
Member
- Joined:
- Jul 2024
- Posts:
- 208
- From:
- Utrecht, NL
OpenVZ hosts are worst offenders. The virtualization tax is hidden in "vCPU" definitions that evaporate at renewal.
- GreenCloudVPS KVM: promo $3.50, renewal $8.99, cgroup v2 limits unchanged
- Leaseweb KVM: promo €4.00, renewal €12.00, actual vCPU reduced from dedicated to burstable
- Time4VPS OpenVZ: promo €2.99, renewal €9.99, "vSwap" redefined to exclude disk cache
Kernel-level transparency required. Check /proc/cpuinfo and /proc/meminfo at purchase and renewal. Document everything. The virtualization tax increases at renewal.
virsh list --all | wc -l: 47
cleardmitri
Moderator
Moderator
- Joined:
- Jun 2024
- Posts:
- 124
- From:
- Riga, LV
What notice period does your contract specify?
No logs, no proof. I have logs.
larryjeong
Member
- Joined:
- Jun 2024
- Posts:
- 179
- From:
- Texas, US
RamNode promo $15/year, renewal $48/year. No notice. Just the charge. I only noticed because my prepaid balance went negative and they suspended the VM.
Texas consumer law worthless for this. Business account by default even when you sign up as individual.
$3/year. 128MB RAM. Pure happiness.
pam3
Member
Latency Witch
- Joined:
- Aug 2024
- Posts:
- 74
- From:
- Melbourne, Australia
RFC 5322 delivery confirmed via MX route to Google Workspace. Intercepted by Promotions tab. Effective notice: zero days.
I now run a cron that screenscrapes billing portals. Sad but necessary.
100% packet loss at hop 3
kate3
Member
- Joined:
- Jul 2024
- Posts:
- 208
- From:
- Utrecht, NL
KVM or OpenVZ? Their OpenVZ 7 templates still show /proc/cpuinfo with fake model name "QEMU Virtual CPU" but the vCPU scheduler changed from fair to throttle-heavy around 2022. Renewal timing correlates with migration to new nodes.
Document /proc/sched_debug before and after. I have.
virsh list --all | wc -l: 47