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? |
|
MacLeech
The one and only
Premium
join:2001-07-14
SoCal
1 edit | 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. |
|
amysheehan
Premium,VIP,MVM
join:1999-12-21
Huntington Beach, CA
 ·RoadRunner Cable
| reply to SoCalResident1
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 |
|
Anonymous_
Anonymous
Premium
join:2004-06-21
127.0.0.1
clubs: | reply to SoCalResident1
just keep renewing tell you get a good ip
may take upto 20 trys
»Delay on ping |
|
MacLeech
The one and only
Premium
join:2001-07-14
SoCal
1 edit | reply to amysheehan
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. |
|
Anonymous_
Anonymous
Premium
join:2004-06-21
127.0.0.1
clubs:
·RoadRunner Cable
·Time Warner Cable
 ·Time Warner VOIP
2 edits | said by MacLeech :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. 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 |
|
SoCalResident1
@rr.com
| reply to SoCalResident1
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. |
|
SoCalResident1
@rr.com
| reply to SoCalResident1
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? |
|
Anonymous_
Anonymous
Premium
join:2004-06-21
127.0.0.1
clubs: | i renewed 75 times with no such luck |
|
SoCalResident1
@rr.com | 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. |
|
MacLeech
The one and only
Premium
join:2001-07-14
SoCal | 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. |
|
Reinvent3d
join:2004-12-06
Camarillo, CA | 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. |
|
Anonymous_
Anonymous
Premium
join:2004-06-21
127.0.0.1
clubs:
·RoadRunner Cable
·Time Warner Cable
·Time Warner VOIP
4 edits | 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 |
|
Reinvent3d
join:2004-12-06
Camarillo, CA
| 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. 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 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. |
|
maartena
Stacked.
Premium
join:2002-05-10
Orange, CA
·RoadRunner Cable
| reply to Anonymous_
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. |
|
Anonymous_
Anonymous
Premium
join:2004-06-21
127.0.0.1
clubs:
·RoadRunner Cable
·Time Warner Cable
·Time Warner VOIP
| 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
|
|
maartena
Stacked.
Premium
join:2002-05-10
Orange, CA
·RoadRunner Cable
| 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! |
|
Anonymous_
Anonymous
Premium
join:2004-06-21
127.0.0.1
clubs:
·RoadRunner Cable
·Time Warner Cable
·Time Warner VOIP
1 edit | 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. 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. getting about 40ms to ucla.edu
Classic ip 76xxxxx 15 to 20ms |
|
MacLeech
The one and only
Premium
join:2001-07-14
SoCal
2 edits | reply to Anonymous_
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. |
|
Anonymous_
Anonymous
Premium
join:2004-06-21
127.0.0.1
clubs:
1 edit |
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] |
|
