One customer's ban lands on one customer

A scraper gives each of ten thousand sessions its own proxy so a ban can't burn the fleet. You run a marketplace tool for three hundred sellers, and you have the opposite problem: you're the honest one, and any single seller can get your IP banned.

Each seller lives in their own container. Each container gets PUT /api/v1/containers/{id}/network with type: socks5 and that seller's own proxy endpoint. Their address, their reputation, applied on the host, nothing configured inside. Seller 212 hammers a vendor API and gets rate-limited; seller 212's exit gets throttled. Seller 40 doesn't notice. Your server's own IP stays clean because it isn't the one talking.

The scraper's trick was evasion. Yours is blast-radius containment: one tenant's behavior can't cost another tenant their integration. Same knob, opposite direction of responsibility.