Shifted my entire edge stack to a single 4C/24GB ARM node. How are you handling egress IP rotation without extra VPS instances?

Hey self-hosters,

just finished rebuilding my cloud edge setup (OCI San Jose ARM instance, 4C/24G, 200GB disk, BBR, Ubuntu 26 LTS).

i almost spun up a tiny secondary AMD instance purely to get a spare IPv4 for heavy downloader tasks (aria2/yt-dlp) that occasionally get IP-throttled by various file-hosting services. in the end, i decided it wasn't worth splitting up my disk IOPS and RAM allocation just for an extra IP.

Instead, i unified everything on the 24GB ARM beast and solved the IP rate-limiting issue on the network layer:

1.IPv6 Subnet Rotation: Binding download tools to rotate requests across the assigned /64 IPv6 block.

2.Containerized WARP Egress: Routing specific Docker containers through a local Cloudflare WARP WireGuard container when dealing with IPv4-only hosts that trigger rate limits.

this keeps my host IPv4 squeaky clean, leaves 20+ GB of RAM for local Docker stacks, and saves me from multi-node sync headaches.

How’s everyone structuring their cloud footprint these days? Single high-spec VPS with smart container routing, or are you still physically separating workloads across small nodes?

https://redd.it/1x22ce0
@r_SelfHosted