Skip to content

Finally left EIG host

Web Hosting by carlos2 4 replies 471 views
7 #1

Six months ago I committed to moving every client off the EIG stack. Documented everything. Staged migrations by traffic tier. Sent 47 transition emails. Zero downtime goal, hit 99.97%. Kept clients in the loop with weekly PDF reports they never read. 🪙

The guilt part: I was an EIG affiliate for three years. Pushed their reseller plans in every "best host" thread I could find. Knew the oversell ratios. Knew the support tickets went to black holes. Still cashed the checks. The affiliate dashboard showed my "lifetime earnings" last week and I felt sick.

Now on Contabo and OVHcloud. Which providers take XMR for annual renewals? Looking to fully detach from traditional payment trails. My clients don't know the backstory. Should I tell them or let the improved uptime speak for itself?

not your keys, not your coins
5 #2

Dude the growth arc here is fire.

Three years and u flipped it around that takes guts.

Otally get the guilt but u fixed it man. Clients see the uptime that matters more than words.

Also OVHcloud takes crypto? I tought only InterServer https://www.interserver.net did XMR!

seedbox, NAS, tape, and three offsite
#3

carlos2 said:
99.97%
Suggests you moved to KVM or at least proper LXC with cgroup v2.

Contabo runs KVM with virtio-net. OVHcloud uses LXC but on a modern kernel with proper blkio throttling. Both handle the noisy neighbor problem better than anything EIG operated.

The affiliate history is ethically compromised but operationally irrelevant now. Your current stack speaks. Don't burden clients with narrative they didn't ask for.

virsh list --all | wc -l: 47
#4

For what it's worth, EIG's network issues went deeper than oversold compute. Their IRR records were stale for years, multiple ASNs with missing or incorrect route objects. RPKI ROAs? Spotty deployment. If you had clients doing any serious outbound, their IP reputation suffered from hijack adjacent space and poor BGP community filtering.

Contabo publishes their communities publicly and filters at the edge. OVHcloud uses RPKI strict mode. Both matter more than most people realize.

Your transition documentation sounds solid. The guilt is yours to carry or release, but the technical debt you cleared for those clients is measurable.

iBGP, eBGP, don't care, just peer
#5

Which OVHcloud kernel version? Their LXC setup matters for blkio.

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft