Slow Download Speeds

[leotitan360]

Hello, i am having problems downloading files from the Nexus. I am a free member and have my adblocker disabled for the Nexus, yet i'm getting 60-120kb/s. This problem also happened two day ago while yesterday the download speeds were back to normal.

After pingin files.nexus-cdn.com, i noticed something is clearly wrong, but i do not know how to proceed from here

Any help is appreciated!

 

 

Disparando files.nexus-cdn.com [195.181.162.41] com 32 bytes de dados:

Esgotado o tempo limite do pedido.

Esgotado o tempo limite do pedido.

Resposta de 195.181.162.41: bytes=32 tempo=122ms TTL=53

Esgotado o tempo limite do pedido.

Estatísticas do Ping para 195.181.162.41:

Pacotes: Enviados = 4, Recebidos = 1, Perdidos = 3 (75% de

perda),

Aproximar um número redondo de vezes em milissegundos:

Mínimo = 122ms, Máximo = 122ms, Média = 122ms

So, i lost 3 packets out of 4, what does that mean?

[tomsite]

That means that somewhere between your PC and the server there is a problem. A ping alone does not provide any information on where this problem occurs. Also there are ISPs that use rate limiting on ICMP packages, which can also result in you seeing lost packages. To delve deeper into where the problem occurs you should first run a basic PING command and if it shows any sign of trouble also use the traceroute command (tracert on windows). It shows hop by hop what the response times are. A hop is every station between you and the destination and issues may occur at any of these hops.

 

Here an example of a traceroute:

 

C:\Users\tom>tracert -d www.nexusmods.com

Tracing route to www.nexusmods.com [104.20.213.63]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.178.1
2 18 ms 17 ms 18 ms 88.77.64.1
3 * 17 ms 17 ms 188.111.189.206
4 18 ms 17 ms 17 ms 92.79.214.236
5 27 ms 25 ms 24 ms 145.254.2.203
6 25 ms 25 ms 25 ms 145.254.2.203
7 * 25 ms 25 ms 80.249.211.140
8 27 ms 26 ms 26 ms 104.20.213.63

Trace complete.

 

In above example you see that i reach Nexus's website after 8 hops (it can be more, but that is a different story and depends on the transfermethod being used between two points, for example some serial, ATM or MPLS connections will not show). BTW the -d parameter disables that the command attempts to resolve all names, i.e. translates each and every IP-Address to a name. Here everything is OK as the responsetimes are grouped nicely together between 17 and 26ms. The * indicates that no response was received, however as said above, ISPs also use rate limiting on ICMP and thus drop some PING packets. It simply saves them a lot of bandwidth and avoids some attacks or at least mitigates them. Let's assume Hop 5 would display 1000ms and more, then you could look up the IP Address and see what ISP has problems. If hops 1-7 are OK but Hop 8 in this example shows excessive response times then the Nexus CDN has an issue.

 

Speaking of which, as Nexus uses a CDN, the shown IP is not the real IP of the server than actually has the content and serves it to you. You might get cases where Hop 8 shows excellent response times, but inside the CDN there is a problem causing slow download speeds for you. To wrap it up in a few sentences, in a CDN multiple servers host the content. Depending from where you access the content, the CDN decides from which server it delivers this content, but it hides the true server from your prying eyes. This increases security and for you it doesn't make a difference.

 

So next time you get slow speeds use the tracert command on WIndows, it will show way better where the issue occurs and is a lot more helpful than a normal PING.PING gives you nothing more than a very rough indication.