Member OP
Hello sirs, need help understanding something. Made VPS last month with Contabo, they say 2GB VSwap. Now dashboard show 2GB RAM. I ask support, they say "same thing bro." But my application crash when before not crash. Very confuse sir, what is difference between VSwap and real RAM? Thank you very much sir
RFC 1122, host requirements. VSwap is AS-path prepending for memory — your provider announces RAM they don't own. Real RAM is your own prefix, no upstream dependency.
Contabo probably oversold on OpenVZ node, burst ballooned, now they're traffic-shaping your allocations. Check if they reallocated your /32 to another tenant.
[Node A] --VSwap--> [Host Kernel] --oom_killer--> [Your Process]
[Node B] --KVM----> [Dedicated] ----stable------> [Your Process]
Get an ASN, run your own anycast, stop renting from resellers without IRR records.
Hey folks, gentle reminder to keep it accessible — not everyone here has their own ASN 🙂
@JokoNord, to put it simply: VSwap is "borrowed" memory that slows way down when the server is busy. Real RAM is yours alone. If Contabo switched your plan without telling you, that's worth asking about directly. They should announce changes like that.
He said no that's the "thinking space." Then KNOWNHOST said we needed more thinking space and charged us double. Is VSwap the same as the thinking space or different? I told my nephew to call KNOWNHOST but he said they're "just the panel guys now."
Member
Guys this is why I stopped pushing OpenVZ plans. Margins look good but churn is brutal when customers figure out their RAM is fake. Any leads on KVM wholesale? Need decent panel too, recieved too many tickets about "slow memory."
JokoNord, check your resolver first — run this before trusting anything Contabo tells you:
dig +short TXT support.contabo.com
Also traceroute to your node, post output. I've seen providers claim "hardware upgrade" when actually they migrated OpenVZ→KVM and your TTL expired mid-propagation. Your "crash" might be oom-killer from different memory accounting, not less RAM. Check dmesg | grep -I kill.
