24 replies to this topic

[YellowHammer]

I have the same ISP as SirYak.  We both used to play lots of games online, but our ISP doubled their latency.   

Pinging yahoo.com [66.94.234.13] with 32 bytes of data:

Reply from 66.94.234.13: bytes=32 time=1394ms TTL=48
Reply from 66.94.234.13: bytes=32 time=1187ms TTL=48
Reply from 66.94.234.13: bytes=32 time=1303ms TTL=47
Reply from 66.94.234.13: bytes=32 time=1323ms TTL=48

Ping statistics for 66.94.234.13:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1187ms, Maximum = 1394ms, Average = 1301ms


I should add, it's not just gaming that's affected by latency.   You should try shopping online (HTTPS), or VPN remote desktop connection.  UGH!   But those "speed" tests sure look good!

[Siryak]

Yah too bad you can only feel that "speed" when you are downloading.

[Sparticus]

Phew, am I glad I have cable or what?

Quote

C:Documents and SettingsSparticus>ping yahoo.com

Pinging yahoo.com [216.109.112.135] with 32 bytes of data:

Reply from 216.109.112.135: bytes=32 time=22ms TTL=56
Reply from 216.109.112.135: bytes=32 time=20ms TTL=56
Reply from 216.109.112.135: bytes=32 time=19ms TTL=56
Reply from 216.109.112.135: bytes=32 time=19ms TTL=56

Ping statistics for 216.109.112.135:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 22ms, Average = 20ms

C:Documents and SettingsSparticus>ping google.com

Pinging google.com [64.233.167.99] with 32 bytes of data:

Reply from 64.233.167.99: bytes=32 time=44ms TTL=246
Reply from 64.233.167.99: bytes=32 time=46ms TTL=246
Reply from 64.233.167.99: bytes=32 time=44ms TTL=246
Reply from 64.233.167.99: bytes=32 time=44ms TTL=246

Ping statistics for 64.233.167.99:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 44ms, Maximum = 46ms, Average = 44ms

C:Documents and SettingsSparticus>ping yahoo.com -n 20

Pinging yahoo.com [216.109.112.135] with 32 bytes of data:

Reply from 216.109.112.135: bytes=32 time=19ms TTL=56
Reply from 216.109.112.135: bytes=32 time=18ms TTL=56
Reply from 216.109.112.135: bytes=32 time=18ms TTL=56
Reply from 216.109.112.135: bytes=32 time=18ms TTL=56
Reply from 216.109.112.135: bytes=32 time=19ms TTL=56
Reply from 216.109.112.135: bytes=32 time=18ms TTL=56
Reply from 216.109.112.135: bytes=32 time=18ms TTL=56
Reply from 216.109.112.135: bytes=32 time=20ms TTL=56
Reply from 216.109.112.135: bytes=32 time=20ms TTL=56
Reply from 216.109.112.135: bytes=32 time=19ms TTL=56
Reply from 216.109.112.135: bytes=32 time=19ms TTL=56
Reply from 216.109.112.135: bytes=32 time=19ms TTL=56
Reply from 216.109.112.135: bytes=32 time=19ms TTL=56
Reply from 216.109.112.135: bytes=32 time=19ms TTL=56
Reply from 216.109.112.135: bytes=32 time=18ms TTL=56
Reply from 216.109.112.135: bytes=32 time=18ms TTL=56
Reply from 216.109.112.135: bytes=32 time=19ms TTL=56
Reply from 216.109.112.135: bytes=32 time=19ms TTL=56
Reply from 216.109.112.135: bytes=32 time=20ms TTL=56
Reply from 216.109.112.135: bytes=32 time=19ms TTL=56

Ping statistics for 216.109.112.135:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 20ms, Average = 18ms

C:Documents and SettingsSparticus>

[Siryak]

Quote

Phew, am I glad I have cable or what?

*Smack!*

[yuddengard]

So, this is mine (I'm a brazilian guy) and look how bad is my connection. I'm on a 1MB cable connection.

ping yahoo.com

Disparando contra yahoo.com [66.94.234.13] com 32 bytes de dados:

Resposta de 66.94.234.13: bytes=32 tempo=192ms TTL=54
Resposta de 66.94.234.13: bytes=32 tempo=191ms TTL=54
Resposta de 66.94.234.13: bytes=32 tempo=207ms TTL=53
Resposta de 66.94.234.13: bytes=32 tempo=189ms TTL=55

Estatísticas do Ping para 66.94.234.13:
    Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de perda),
Aproximar um número redondo de vezes em milissegundos:
    Mínimo = 189ms, Máximo = 207ms, Média = 194ms

Brazil connections are far away from a good solution. At least for now. Unfortunating.