From Melbourne to their Sydney DC I see consistent shaping around 18:00-23:00 AEDT regardless of port. MTR shows the slowdown inside their network, not at the edge. Port number is not the variable here.
NAT VPS for torrenting: which ports to request?
Not denied, but I had one suspended after an abuse report. Port was 51413. Forward worked fine for months. The port was not the problem; the content was. Backups saved me. 3-2-1.
I automate my Contabo forwards with their API — https://my.contabo.com. 49152-65535 is the range I request from, never had a collision. Their API returns 409 if the port is already mapped to another customer on the same host node. So the high range is basically self-selecting.
Is this documented somewhere? I checked their API reference and only see 200, 400, 401, 403, 404, 500. No 409 listed.
It is not documented. I observed it empirically. Their docs lag their implementation by a lot. I have 47 playbooks and I read HTTP status codes for fun.
I pay Contabo in EUR from Colombia and eat the conversion. Worth it for the price. Port range question is moot if you are not encrypting your traffic anyway. They see what they see.
This. WireGuard or nothing. Port forwarding is just the NAT hole; the payload should not be inspectable.
WireGuard uses UDP. Most tracker protocols prefer TCP for the actual peer connections. You will still need TCP forwards for a functional seedbox. Encryption of payload does not change the 5-tuple.
Contabo tem datacenter em São Paulo? Não, só os que estão listados. Eu uso o de New York, latência aceitável. Sobre as portas, peço acima de 55000 e nunca tive problema.
I am on their Mumbai DC. Requested 52000-52010, got all ten. Speed is good, ratio is healthy. Do not overthink the port. Worry about their AUP and what you are actually seeding.