MacLeech
The one and only
Premium
join:2001-07-14
SoCal
2 edits | reply to Anonymous_
Re: [TWC] SoCal IP Change, Higher Ping
Post the ENTIRE trace route. A single hop is USELESS.
Lets see if you can keep on task too. Everytime you bring any issue up, your ADD kicks in after a few posts, and you go off on something else to be forgotten later...
»www2.dslreports.com/forum/r21060···-on-ping |
|
Reinvent3d
join:2004-12-06
Camarillo, CA
| And that means what punker? lol
OH NO! One hop and 11ms increase!!!
Yes, it's going to fluctuate, but my point that I was making that a 7ms increase from 1 IP to another is negligible and not noticeable in games. And no one cares about Nintendo 64 emulators online...that's just stupid.
Yes, pings vary greatly between in-game, where stuff is actually happening, compared to pinging a server list. Please, do us all a favor and go learn something about networking. May save us all a lot of time trying to explain something to you, that you probably can't comprehend anyway. |
|
Anonymous_
Anonymous
Premium
join:2004-06-21
127.0.0.1
clubs:
 ·RoadRunner Cable
·Time Warner Cable
 ·Time Warner VOIP
1 edit | reply to MacLeech
said by MacLeech  :Post the ENTIRE trace route. A single hop is USELESS. Lets see if you can keep on task too. Everytime you bring any issue up, your ADD kicks in after a few posts, and you go off on something else to be forgotten later... » www2.dslreports.com/forum/r21060···-on-ping increasing the TX power helped a bit
ucla.edu
Ping statistics for 169.232.33.224:
Packets: Sent = 35, Received = 35, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 32ms, Average = 23ms
|
|
maartena
Stacked.
Premium
join:2002-05-10
Orange, CA
·RoadRunner Cable
| Looks like you have pretty good pings there punker, seeing as DSLReports is on the east coast and you are on the west coast.
Again a small compare from my big phat business pipe at work:
Pinging dslreports.com [209.123.109.175] with 32 bytes of data:
Reply from 209.123.109.175: bytes=32 time=146ms TTL=52
Reply from 209.123.109.175: bytes=32 time=100ms TTL=52
Reply from 209.123.109.175: bytes=32 time=104ms TTL=52
Reply from 209.123.109.175: bytes=32 time=116ms TTL=52
Reply from 209.123.109.175: bytes=32 time=119ms TTL=52
Reply from 209.123.109.175: bytes=32 time=119ms TTL=52
Reply from 209.123.109.175: bytes=32 time=100ms TTL=52
Reply from 209.123.109.175: bytes=32 time=114ms TTL=52
Reply from 209.123.109.175: bytes=32 time=119ms TTL=52
Reply from 209.123.109.175: bytes=32 time=152ms TTL=52
Reply from 209.123.109.175: bytes=32 time=100ms TTL=52
Reply from 209.123.109.175: bytes=32 time=128ms TTL=52
Reply from 209.123.109.175: bytes=32 time=152ms TTL=52
Ping statistics for 209.123.109.175:
Packets: Sent = 13, Received = 13, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 100ms, Maximum = 152ms, Average = 120ms
Also from the LA area.
You have NOTHING to complain about on that ping and traceroute. It looks pretty much spot on what it should be.
--
Obama 2008 - Because McCain is more of the same! |
|
LADude1
@rr.com | reply to SoCalResident1
So do ip changes happen at random? I don't want a 50% ping increase .... |
|
