[TWC] SoCal IP Change, Higher Ping

Forums » US Cable Support » Road Runner » [TWC] SoCal IP Change, Higher Ping


Uniqs: 923	Share Topic:	RSS topic:	toggle: flat / full normal / watch	Posting:	Post a:	Post a:

Links: ·Web page ·Network Status ·RR FORUM FAQ ·Cable Users FAQ ·Tweaks ·Broadband Modem

Poor speeds 40% packet loss »
« [TWC] Can only connect throught router - not through modem

SoCalResident1 @rr.com	[TWC] SoCal IP Change, Higher Ping Hello, I got on today and noticed my ip changed from 75...* to 98.149.183.* so I went to speedtest .net to check my speeds and my recommended server was Kansas City, MO. This is my results I'm in Socal(93030), anybody know what happend?? What should I do?
	permalink · 2008-10-02 17:44:57 ·

MacLeech
The one and only
Premium
join:2001-07-14
SoCal

1 edit

Re: [TWC] SoCal IP Change, Higher Ping

It's a different IP block not properly ID'd by outside geo sites which is why your closest speedtest site is said to be Kansas.

More that likely the return routing is probably taking a different path back to you which is why the ping is slightly higher.

There's nothing to do if it's working fine for you.

If it's really a problem, change the MAC address of the device connected to the modem and reset the modem to get a new IP.

permalink · 2008-10-02 17:52:56 ·

amysheehan
Premium,VIP,MVM
join:1999-12-21
Huntington Beach, CA

·RoadRunner Cable

said by SoCalResident1 :

Hello, I got on today and noticed my ip changed from 75.*.*.* to 98.149.183.* so I went to speedtest .net to check my speeds and my recommended server was Kansas City, MO. This is my results

I'm in Socal(93030), anybody know what happend?? What should I do?

Try this link to see if your new IP is better identified -
»ip-address.cc/

There have been other SoCal rr customers who have posted in this forum recently that they were moved to the 98 block as well. It took some sites a while before they were ID'd properly -

--
Proud Member of ASAP
DSLR Phishtracker

permalink · 2008-10-02 17:59:39 · Print ·

MacLeech
The one and only
Premium
join:2001-07-14
SoCal

1 edit

Re: [TWC] SoCal IP Change, Higher Ping

said by amysheehan

:

Try this link to see if your new IP is better identified -
»ip-address.cc/

There have been other SoCal rr customers who have posted in this forum recently that they were moved to the 98 block as well. It took some sites a while before they were ID'd properly -

There are also Verizon FIOS customers with the SAME complaint about the "new" 98 block IPs they've received. It's not particular to TWC/RR.

permalink · 2008-10-02 18:03:24 · Print ·

Anonymous_
Anonymous
Premium
join:2004-06-21
127.0.0.1
clubs:

Re: [TWC] SoCal IP Change, Higher Ping

said by MacLeech

said by amysheehan

There are also Verizon FIOS customers with the SAME complaint about the "new" 98 block IPs they've received. It's not particular to TWC/RR.

The NEW IP RANGE SUCKS ass

THE PING TIME IS 50% HIGHER then the old ip range

to LA the old ip range is 15ms to 19ms

NEW IP RANGE 30 to 35ms includes huge LAG spikes upto 800ms

it also affects download and upload speeds to many sites

even if you do get a GOOD working ip the LAG SPIKES ARE THERE

permalink · 2008-10-02 18:06:31 · Print ·

Anonymous_ Anonymous Premium join:2004-06-21 127.0.0.1 clubs:	just keep renewing tell you get a good ip may take upto 20 trys »Delay on ping
	permalink · 2008-10-02 18:01:18 ·

SoCalResident1 @rr.com	Why did this happen to me . This sucks man, I'm a gamer and my ping to LA servers used to be around 18-23, now it's over 30 . I'm just going to keep renewing my ip, hope it works.
	permalink · 2008-10-02 18:27:40 ·

SoCalResident1 @rr.com	It took me a lot of tries, but I got my ip back to 75.82.. ping went down some, but not like before =/. Do you guys think I can get my ping back to normal if I keep renewing?
	permalink · 2008-10-02 18:37:56 ·

Anonymous_ Anonymous Premium join:2004-06-21 127.0.0.1 clubs:	Re: [TWC] SoCal IP Change, Higher Ping i renewed 75 times with no such luck
	permalink · 2008-10-02 20:45:18 ·

SoCalResident1 @rr.com	Re: [TWC] SoCal IP Change, Higher Ping Makes me mad that my 10M connection now has the same ping as my 1.5M dsl connection I had a couple of months ago.
	permalink · 2008-10-02 20:51:43 ·

MacLeech The one and only Premium join:2001-07-14 SoCal	Re: [TWC] SoCal IP Change, Higher Ping said by SoCalResident1 : Makes me mad that my 10M connection now has the same ping as my 1.5M dsl connection I had a couple of months ago. Bandwidth has little bearing on latency.
	permalink · 2008-10-02 23:07:09 ·

Reinvent3d join:2004-12-06 Camarillo, CA	Re: [TWC] SoCal IP Change, Higher Ping Oh no! Your ping is a bit over 30! Sorry to say, but you really can't see the difference between those 10ms or less. And guaranteed, your ping is probably higher than that while in-game, as opposed to just pinging a server list.
	permalink · 2008-10-02 23:30:47 ·

Anonymous_
Anonymous
Premium
join:2004-06-21
127.0.0.1
clubs:

Re: [TWC] SoCal IP Change, Higher Ping

said by Reinvent3d

:

And guaranteed, your ping is probably higher than that while in-game, as opposed to just pinging a server list.

you must have a very old computer if that happions

said by Reinvent3d

:

Oh no! Your ping is a bit over 30! Sorry to say, but you really can't see the difference between those 10ms or less.

if it's jumping around all over the place you get kicked out for desynching or temporarily ban from the server

when playing PC game

Reply from xx.xxx.xxx.xx: bytes=32 time=98ms TTL=44
Reply from xx.xxx.xxx.xx: bytes=32 time=100ms TTL=44
Reply from xx.xxx.xxx.xx: bytes=32 time=100ms TTL=44
Reply from xx.xxx.xxx.xx: bytes=32 time=100ms TTL=44
Reply from xx.xxx.xxx.xx: bytes=32 time=100ms TTL=44
Reply from xx.xxx.xxx.xx: bytes=32 time=97ms TTL=44
Reply from xx.xxx.xxx.xx: bytes=32 time=99ms TTL=44
Reply from xx.xxx.xxx.xx: bytes=32 time=93ms TTL=44
Reply from xx.xxx.xxx.xx: bytes=32 time=92ms TTL=44
Reply from xx.xxx.xxx.xx: bytes=32 time=93ms TTL=44
Reply from xx.xxx.xxx.xx: bytes=32 time=93ms TTL=44

stoped PC game

Reply from xx.xxx.xxx.xx: bytes=32 time=96ms TTL=45
Reply from xx.xxx.xxx.xx: bytes=32 time=94ms TTL=45
Reply from xx.xxx.xxx.xx: bytes=32 time=91ms TTL=45
Reply from xx.xxx.xxx.xx: bytes=32 time=91ms TTL=45
Reply from xx.xxx.xxx.xx: bytes=32 time=101ms TTL=45
Reply from xx.xxx.xxx.xx: bytes=32 time=95ms TTL=45
Reply from xx.xxx.xxx.xx: bytes=32 time=94ms TTL=45
Reply from xx.xxx.xxx.xx: bytes=32 time=94ms TTL=45
Reply from xx.xxx.xxx.xx: bytes=32 time=107ms TTL=45
Reply from xx.xxx.xxx.xx: bytes=32 time=106ms TTL=45
Reply from xx.xxx.xxx.xx: bytes=32 time=100ms TTL=45

permalink · 2008-10-02 23:55:07 · Print ·

Reinvent3d

join:2004-12-06
Camarillo, CA

Re: [TWC] SoCal IP Change, Higher Ping

said by Anonymous_

said by Reinvent3d

:

And guaranteed, your ping is probably higher than that while in-game, as opposed to just pinging a server list.

you must have a very old computer if that happions

said by Reinvent3d

:

Oh no! Your ping is a bit over 30! Sorry to say, but you really can't see the difference between those 10ms or less.

No, I'll give you a perfect example of where it's higher in-game. Counter-Strike: Source. Your actual ping varies greatly than what the score board actually says. Server side, it's higher.

I doubt this ping was jumping. But you obviously didn't listen to what I said punker. What I said was that you can't tell the difference between 18-23ms and 30ms. You really can't. I didn't say anything about it jumping at all. And you need to keep in mind, pings aren't always going to be constant. There's routing involved, and many other factors involved. Him changing his IP address was such a tiny small problem. OH NO! 7ms higher! Big freaking deal. Again, you can't even tell the difference between that.

permalink · 2008-10-03 01:59:04 · Print ·

maartena
Stacked.
Premium
join:2002-05-10
Orange, CA

·RoadRunner Cable

said by Anonymous_

:

i renewed 75 times with no such luck

You have no life if you actually have time for that.

On the topic at hand: Latency from one point to another is only affected by the ROUTE your packet takes, not by the IP address. Now, it is very possible that the new IP addresses take a different route to get to your destination, but that isn't to say the route won't change.

That being said, a latency change from 15ms to 30-35ms really does not make a lot of difference, if any at all in online gaming.

Furthermore, it is nice you just put xx.xxx.xxx.xx punker, but that doesn't mean ANYTHING to us as none of us can see what server you are trying to ping.

permalink · 2008-10-03 12:12:18 · Print ·

Anonymous_
Anonymous
Premium
join:2004-06-21
127.0.0.1
clubs:

·RoadRunner Cable

·Time Warner Cable

·Time Warner VOIP

Re: [TWC] SoCal IP Change, Higher Ping

said by maartena

said by Anonymous_

:

i renewed 75 times with no such luck

You have no life if you actually have time for that.

it only took 10-15min to do

Nintendo 64 Emulator

said by maartena

said by Anonymous_

:

......

That being said, a latency change from 15ms to 30-35ms really does not make a lot of difference, if any at all in online gaming.

it is noticeable on Nintendo 64 Emulator online

said by maartena

said by Anonymous_

:

.........

Furthermore, it is nice you just put xx.xxx.xxx.xx punker, but that doesn't mean ANYTHING to us as none of us can see what server you are trying to ping.

66.197.126.19
--------------------------------------------
back on topic

the tech that came over claimed that

it was a ports issues and that it was on there end

permalink · 2008-10-03 16:03:32 · Print ·

maartena
Stacked.
Premium
join:2002-05-10
Orange, CA

·RoadRunner Cable

Re: [TWC] SoCal IP Change, Higher Ping

Pinging 66.197.126.19 with 32 bytes of data:
Reply from 66.197.126.19: bytes=32 time=71ms TTL=58
Reply from 66.197.126.19: bytes=32 time=76ms TTL=58
Reply from 66.197.126.19: bytes=32 time=91ms TTL=58
Reply from 66.197.126.19: bytes=32 time=93ms TTL=58

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

That is using my business internet line at work: A 15 Mbps up/down Ethernet hand-off. Very fast.

The IP adress mentioned is in Ashburn, VA - on the east coast. You aren't going to get anything better then about 70ms on that, simply because of the physical distance.

I am pinging from Los Angeles area.

Do a ping on ucla.edu and see what you get. It should be 25 to 30ms, which is NORMAL for the LA area, if you are IN the LA area.
--
Obama 2008 - Because McCain is more of the same!

permalink · 2008-10-03 16:11:01 · Print ·

Anonymous_
Anonymous
Premium
join:2004-06-21
127.0.0.1
clubs:

Re: [TWC] SoCal IP Change, Higher Ping

said by maartena

:

Pinging 66.197.126.19 with 32 bytes of data:
Reply from 66.197.126.19: bytes=32 time=71ms TTL=58
Reply from 66.197.126.19: bytes=32 time=76ms TTL=58
Reply from 66.197.126.19: bytes=32 time=91ms TTL=58
Reply from 66.197.126.19: bytes=32 time=93ms TTL=58

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

That is using my business internet line at work: A 15 Mbps up/down Ethernet hand-off. Very fast.

getting about 40ms to ucla.edu

Classic ip 76xxxxx 15 to 20ms

permalink · 2008-10-03 16:15:51 · Print ·

MacLeech
The one and only
Premium
join:2001-07-14
SoCal

2 edits

said by Anonymous_

:

it was a ports issues and that it was on there end

3 things would show otherwise.

1. Verizon FIOS is affected by a similar issue.
2. Trace routes and pings show otherwise. Different protocol, no ports involved, same issue.
3. Routers mid path don't usually check the source or destination port and that is where the changes in lantecy is happening.

Use PingPlotter and reverse traces to pinpoint WHERE the increase is happening.

permalink · 2008-10-03 16:25:35 · Print ·

Anonymous_ Anonymous Premium join:2004-06-21 127.0.0.1 clubs: 1 edit	Re: [TWC] SoCal IP Change, Higher Ping 40ms bad ip telia-level3-ge.LosAngeles1.level3.net [4.68.110 .222] 29ms good ip telia-level3-ge.LosAngeles1.level3.net [4.68.110 .222]
	permalink · 2008-10-03 16:33:22 ·

MacLeech The one and only Premium join:2001-07-14 SoCal 2 edits	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
	permalink · 2008-10-03 16:38:47 ·

Reinvent3d

join:2004-12-06
Camarillo, CA

Re: [TWC] SoCal IP Change, Higher Ping

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.

permalink · 2008-10-03 16:40:55 · Print ·

Anonymous_
Anonymous
Premium
join:2004-06-21
127.0.0.1
clubs:

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

C:\Documents and Settings\Administrator>ping -t dslreports.com
 
Pinging dslreports.com [209.123.109.175] with 32 bytes of data:
 
Reply from 209.123.109.175: bytes=32 time=105ms TTL=42
Reply from 209.123.109.175: bytes=32 time=106ms TTL=42
Reply from 209.123.109.175: bytes=32 time=105ms TTL=42
Reply from 209.123.109.175: bytes=32 time=120ms TTL=42
Reply from 209.123.109.175: bytes=32 time=107ms TTL=42
Reply from 209.123.109.175: bytes=32 time=103ms TTL=42
Reply from 209.123.109.175: bytes=32 time=108ms TTL=42
Reply from 209.123.109.175: bytes=32 time=104ms TTL=42
Reply from 209.123.109.175: bytes=32 time=107ms TTL=42
Reply from 209.123.109.175: bytes=32 time=106ms TTL=42
Reply from 209.123.109.175: bytes=32 time=103ms TTL=42
Reply from 209.123.109.175: bytes=32 time=113ms TTL=42
Reply from 209.123.109.175: bytes=32 time=105ms TTL=42
Reply from 209.123.109.175: bytes=32 time=114ms TTL=42
Reply from 209.123.109.175: bytes=32 time=104ms TTL=42
Reply from 209.123.109.175: bytes=32 time=107ms TTL=42
Reply from 209.123.109.175: bytes=32 time=104ms TTL=42
Reply from 209.123.109.175: bytes=32 time=106ms TTL=42
Reply from 209.123.109.175: bytes=32 time=102ms TTL=42
Reply from 209.123.109.175: bytes=32 time=105ms TTL=42
Reply from 209.123.109.175: bytes=32 time=106ms TTL=42
Reply from 209.123.109.175: bytes=32 time=104ms TTL=42
Reply from 209.123.109.175: bytes=32 time=106ms TTL=42
Reply from 209.123.109.175: bytes=32 time=106ms TTL=42
Reply from 209.123.109.175: bytes=32 time=104ms TTL=42
Reply from 209.123.109.175: bytes=32 time=104ms TTL=42
Reply from 209.123.109.175: bytes=32 time=117ms TTL=42
Reply from 209.123.109.175: bytes=32 time=107ms TTL=42
Reply from 209.123.109.175: bytes=32 time=105ms TTL=42
Reply from 209.123.109.175: bytes=32 time=104ms TTL=42
Reply from 209.123.109.175: bytes=32 time=107ms TTL=42
Reply from 209.123.109.175: bytes=32 time=107ms TTL=42
Reply from 209.123.109.175: bytes=32 time=103ms TTL=42
Reply from 209.123.109.175: bytes=32 time=107ms TTL=42
Reply from 209.123.109.175: bytes=32 time=105ms TTL=42
Reply from 209.123.109.175: bytes=32 time=106ms TTL=42
Reply from 209.123.109.175: bytes=32 time=107ms TTL=42
Reply from 209.123.109.175: bytes=32 time=106ms TTL=42
 
Ping statistics for 209.123.109.175:
    Packets: Sent = 38, Received = 38, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 102ms, Maximum = 120ms, Average = 106ms
Control-C
^C
C:\Documents and Settings\Administrator>tracert dslreports.com
 
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  DD-WRT [192.168.1.1]
  2    18 ms    10 ms     8 ms  cpe-98-148-208-1.socal.res.rr.com [98.148.208.1]
 
  3    12 ms    12 ms    12 ms  gig1-16.pldlca1-swt1.socal.rr.com [76.167.11.41]
 
  4    10 ms    13 ms     8 ms  cpe-76-167-11-105.socal.res.rr.com [76.167.11.10
5]
  5    16 ms    16 ms    12 ms  gig2-2.lsanca3-rtr1.socal.rr.com [76.167.2.34]
  6    24 ms    14 ms    13 ms  prt22.vnnyca2-rtr2.socal.rr.com [76.167.2.13]
  7    26 ms    26 ms    24 ms  tge9-3.lamdca1-swt1.socal.rr.com [76.167.2.52]
  8    34 ms    25 ms    21 ms  tge4-0-0.lsanca1-rtr1.socal.rr.com [76.167.2.56]
 
  9     *        *        *     Request timed out.
 10    26 ms    25 ms    27 ms  te-3-1.car1.Tustin1.Level3.net [4.71.104.149]
 11    43 ms    27 ms    27 ms  ae-2-3.bar1.Tustin1.Level3.net [4.69.132.218]
 12    44 ms    34 ms    35 ms  ae-6-6.ebr1.LosAngeles1.Level3.net [4.69.136.202
]
 13    30 ms    34 ms    36 ms  ae-81-81.csw3.LosAngeles1.Level3.net [4.69.137.1
0]
 14    28 ms    25 ms    25 ms  ae-33-89.car3.LosAngeles1.Level3.net [4.68.20.13
3]
 15    37 ms    37 ms    35 ms  telia-level3-ge.LosAngeles1.level3.net [4.68.110
.222]
 16   101 ms   105 ms   103 ms  nyk-bb1-link.telia.net [80.91.252.162]
 17   106 ms   111 ms   102 ms  nyk-b3-link.telia.net [80.91.248.174]
 18   102 ms   104 ms   103 ms  nac-110814-nyk-b3.c.telia.net [213.248.82.94]
 19   107 ms   106 ms   112 ms  0.e1-1.tbr2.ewr.nac.net [209.123.10.133]
 20   104 ms   106 ms   104 ms  0.e1-4.tbr2.oct.nac.net [209.123.10.126]
 21   106 ms   105 ms   105 ms  vlan808.esd1.oct.nac.net [209.123.10.42]
 22   110 ms   103 ms   104 ms  www.dslreports.com [209.123.109.175]
 
Trace complete.
 
Trace complete.

good ip
 
C:\Documents and Settings\Administrator>tracert dslreports.com
 
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  DD-WRT [192.168.1.1]
  2    13 ms    12 ms     9 ms  cpe-98-148-208-1.socal.res.rr.com [98.148.208.1]
 
  3     9 ms    12 ms    14 ms  gig1-16.pldlca1-swt1.socal.rr.com [76.167.11.41]
 
  4    11 ms     8 ms     9 ms  cpe-76-167-11-105.socal.res.rr.com [76.167.11.10
5]
  5    12 ms    17 ms    12 ms  gig2-2.lsanca3-rtr1.socal.rr.com [76.167.2.34]
  6    12 ms    13 ms    13 ms  prt32.lsanca3-rtr1.socal.rr.com [76.167.2.21]
  7     *        *        *     Request timed out.
  8    16 ms    17 ms    17 ms  te-1-4.car1.Tustin1.Level3.net [4.79.140.1]
  9    20 ms    16 ms    16 ms  ae-2-3.bar1.Tustin1.Level3.net [4.69.132.218]
 10    19 ms    16 ms    18 ms  ae-6-6.ebr1.LosAngeles1.Level3.net [4.69.136.202
]
 11    38 ms    20 ms    32 ms  ae-81-81.csw3.LosAngeles1.Level3.net [4.69.137.1
0]
 12    18 ms    17 ms    19 ms  ae-33-89.car3.LosAngeles1.Level3.net [4.68.20.13
3]
 13    32 ms    31 ms    28 ms  telia-level3-ge.LosAngeles1.level3.net [4.68.110
.222]
 14    84 ms    89 ms    86 ms  nyk-bb1-link.telia.net [80.91.252.226]
 15    93 ms    86 ms    92 ms  nyk-b3-link.telia.net [80.91.248.174]
 16    86 ms    85 ms    88 ms  nac-112088-nyk-b3.c.telia.net [213.248.83.74]
 17    88 ms    84 ms    87 ms  0.e1-1.tbr1.ewr.nac.net [209.123.10.129]
 18    94 ms    87 ms   100 ms  0.e1-4.tbr1.oct.nac.net [209.123.10.122]
 19    89 ms    89 ms    88 ms  vlan804.esd1.oct.nac.net [209.123.10.2]
 20    88 ms    88 ms    89 ms  www.dslreports.com [209.123.109.175]
 
Trace complete.
 
C:\Documents and Settings\Administrator>tracert dslreports.com
 
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  DD-WRT [192.168.1.1]
  2    10 ms     9 ms    11 ms  cpe-98-148-208-1.socal.res.rr.com [98.148.208.1]
 
  3     8 ms     8 ms     7 ms  gig1-16.pldlca1-swt1.socal.rr.com [76.167.11.41]
 
  4    11 ms     9 ms     7 ms  cpe-76-167-11-105.socal.res.rr.com [76.167.11.10
5]
  5    15 ms    13 ms    13 ms  gig2-2.lsanca3-rtr1.socal.rr.com [76.167.2.34]
  6    13 ms    21 ms    13 ms  prt32.lsanca3-rtr1.socal.rr.com [76.167.2.21]
  7     *        *        *     Request timed out.
  8    19 ms    18 ms    15 ms  te-3-1.car1.Tustin1.Level3.net [4.71.104.149]
  9    18 ms    15 ms    17 ms  ae-2-3.bar1.Tustin1.Level3.net [4.69.132.218]
 10    27 ms    33 ms    20 ms  ae-6-6.ebr1.LosAngeles1.Level3.net [4.69.136.202
]
 11    21 ms    19 ms    30 ms  ae-81-81.csw3.LosAngeles1.Level3.net [4.69.137.1
0]
 12    19 ms    16 ms    17 ms  ae-33-89.car3.LosAngeles1.Level3.net [4.68.20.13
3]
 13    29 ms    38 ms    31 ms  telia-level3-ge.LosAngeles1.level3.net [4.68.110
.222]
 14    85 ms    84 ms    87 ms  nyk-bb1-link.telia.net [80.91.252.226]
 15    97 ms    89 ms    87 ms  nyk-b3-link.telia.net [80.91.248.174]
 16    86 ms    85 ms    86 ms  nac-112088-nyk-b3.c.telia.net [213.248.83.74]
 17   101 ms    85 ms    89 ms  0.e1-1.tbr1.ewr.nac.net [209.123.10.129]
 18    88 ms    89 ms    90 ms  0.e1-4.tbr1.oct.nac.net [209.123.10.122]
 19    88 ms    86 ms    88 ms  vlan804.esd1.oct.nac.net [209.123.10.2]
 20    88 ms    86 ms    85 ms  www.dslreports.com [209.123.109.175]

permalink · 2008-10-03 17:40:15 · Print ·

maartena
Stacked.
Premium
join:2002-05-10
Orange, CA

·RoadRunner Cable

Re: [TWC] SoCal IP Change, Higher Ping

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!

permalink · 2008-10-03 18:51:26 · Print ·

LADude1 @rr.com	So do ip changes happen at random? I don't want a 50% ping increase ....
	permalink · 2008-10-06 21:07:47 ·

your comment..

Forums » US Cable Support » Road Runner	Poor speeds 40% packet loss » « [TWC] Can only connect throught router - not through modem


Friday, 27-Nov 06:17:55	Terms of Use \| Privacy Policy \| Hosting by www.nac.net - DSL,Hosting & Co-lo \| feedback \| contact over 10 years online! © 1999-2009 dslreports.com. republican-creole page compression OFF