| High pings said by jca2050:
When it's not lagged its usually in the 30s
That's the problem...consistency. While I get better speeds from Unplugged, recent latency issues are making me concerned about the direction of their service. Don't get me wrong...Unplugged is a great service and IMHO the best option for residents of Horsethief Canyon Ranch but I'm just a whiner  who wants everything perfect in an imperfect world. I've also found that Verizon's DNS servers result in slightly lower pings so that may be something you guys can try.
Verizon's DNS servers
4.2.2.1
4.2.2.2
4.2.2.3
UNPLUGGED (Unplugged's DNS Server)
Pinging www.mplayer.com [207.38.1.155] with 32 bytes of data:
Reply from 207.38.1.155: bytes=32 time=150ms TTL=51
Reply from 207.38.1.155: bytes=32 time=211ms TTL=51
Reply from 207.38.1.155: bytes=32 time=33ms TTL=51
Reply from 207.38.1.155: bytes=32 time=80ms TTL=51
Reply from 207.38.1.155: bytes=32 time=51ms TTL=51
Reply from 207.38.1.155: bytes=32 time=426ms TTL=51
Reply from 207.38.1.155: bytes=32 time=35ms TTL=51
Reply from 207.38.1.155: bytes=32 time=92ms TTL=51
Reply from 207.38.1.155: bytes=32 time=65ms TTL=51
Reply from 207.38.1.155: bytes=32 time=29ms TTL=51
Ping statistics for 207.38.1.155:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 426ms, Average = 117ms
COASTINET (Verizon's DNS servers)
Pinging www.mplayer.com [207.38.1.155] with 32 bytes of data:
Reply from 207.38.1.155: bytes=32 time=78ms TTL=49
Reply from 207.38.1.155: bytes=32 time=55ms TTL=49
Reply from 207.38.1.155: bytes=32 time=55ms TTL=49
Reply from 207.38.1.155: bytes=32 time=59ms TTL=49
Reply from 207.38.1.155: bytes=32 time=56ms TTL=49
Reply from 207.38.1.155: bytes=32 time=57ms TTL=49
Reply from 207.38.1.155: bytes=32 time=72ms TTL=49
Reply from 207.38.1.155: bytes=32 time=59ms TTL=49
Reply from 207.38.1.155: bytes=32 time=54ms TTL=49
Reply from 207.38.1.155: bytes=32 time=84ms TTL=49
Ping statistics for 207.38.1.155:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 54ms, Maximum = 84ms, Average = 62ms
[text was edited by author 2002-06-30 23:34:41] |
|
jca2050Premium
join:2002-02-04
Hacienda Heights, CA | Yeah, I'm really into FPS games like Quake 3, UT, JK2 etc.. and they require low stable ping to play competitively. Lately it's been real difficult to play.  |
|
jca2050Premium
join:2002-02-04
Hacienda Heights, CA Reviews:
 ·Verizon FiOS
| Pinging eof.qwca.net [64.208.50.10] with 32 bytes of data:
Reply from 64.208.50.10: bytes=32 time=130ms TTL=246
Reply from 64.208.50.10: bytes=32 time=100ms TTL=246
Reply from 64.208.50.10: bytes=32 time=260ms TTL=246
Reply from 64.208.50.10: bytes=32 time=461ms TTL=246
This server is usually in the 30s |
|
| Well, I'm doing a little better as the evening wears on. Earlier I woudld get spikes up to 400ms from Unplugged. Coastinet has been pretty consistent this evening.
Unplugged
Pinging 64.208.50.10 with 32 bytes of data:
Reply from 64.208.50.10: bytes=32 time=46ms TTL=245
Reply from 64.208.50.10: bytes=32 time=49ms TTL=245
Reply from 64.208.50.10: bytes=32 time=57ms TTL=245
Reply from 64.208.50.10: bytes=32 time=51ms TTL=245
Reply from 64.208.50.10: bytes=32 time=91ms TTL=245
Reply from 64.208.50.10: bytes=32 time=44ms TTL=245
Reply from 64.208.50.10: bytes=32 time=35ms TTL=245
Reply from 64.208.50.10: bytes=32 time=52ms TTL=245
Reply from 64.208.50.10: bytes=32 time=46ms TTL=245
Reply from 64.208.50.10: bytes=32 time=36ms TTL=245
Ping statistics for 64.208.50.10:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 91ms, Average = 50ms
Coastinet
Pinging 64.208.50.10 with 32 bytes of data:
Reply from 64.208.50.10: bytes=32 time=88ms TTL=242
Reply from 64.208.50.10: bytes=32 time=47ms TTL=242
Reply from 64.208.50.10: bytes=32 time=46ms TTL=242
Reply from 64.208.50.10: bytes=32 time=75ms TTL=242
Reply from 64.208.50.10: bytes=32 time=94ms TTL=242
Reply from 64.208.50.10: bytes=32 time=88ms TTL=242
Reply from 64.208.50.10: bytes=32 time=88ms TTL=242
Reply from 64.208.50.10: bytes=32 time=78ms TTL=242
Reply from 64.208.50.10: bytes=32 time=66ms TTL=242
Reply from 64.208.50.10: bytes=32 time=60ms TTL=242
Ping statistics for 64.208.50.10:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 94ms, Average = 73ms |
|
jca2050Premium
join:2002-02-04
Hacienda Heights, CA | Do you have Quake 3 or Jedi Knight 2 installed? If I run a server can you try and connect to it?  |
|
|
|
| reply to jca2050
I've not been playing that much lately as my work hours have changed. But when I was playing SoF2 at home I would always choose Unplugged over Coastinet because Unplugged usually had better, more consistent latency. But I guess that isn't the case any longer. Coastinet seems to be in the 80's all the time, day or night where Unplugged will get erratic during the peak usage hours...when I would be trying to play. It's still a great service though...and will be even better if they do their speed upgrade. |
|
| reply to jca2050
JK2 is Jedi Outcast...then yes. I have Q3 and TA but neither are installed. I'm also running SOAF, MOAAA, UT2K3, Ghost Recon and Tac Ops.
[text was edited by author 2002-07-01 00:41:33] |
|
jca2050Premium
join:2002-02-04
Hacienda Heights, CA Reviews:
·Verizon FiOS
| Ohh, Ut2k3, I have the new build 927, its not bad. You should msg me on AIM (jca2050). I can start a listen server and we can play.
You can play multiplayer with it if you download this file I have and edit the ut2.ini file. |
|
jca2050Premium
join:2002-02-04
Hacienda Heights, CA
| I just threw up a Jedi Outcast server if you want to try to connect to it. Connecting to dm4.org should work since it redirects to my ip. If not then 64.243.81.243.
[text was edited by author 2002-07-01 00:53:03] |
|
| I tried connecting but I get parse errors right after connecting. |
|
jca2050Premium
join:2002-02-04
Hacienda Heights, CA | reply to jca2050
I noticed you just tried to connect, you probably need the 1.03a patch, you can grab it at fileplanet.com. I can also send it to you if you want. |
|
| Oh yeah...hold on. I'm getting it. |
|
 guhunaR.I.P MikePremium
join:2001-03-31
Truckee, CA
 ·Covad Communicat..
| reply to Count Hogula$
one other thing is, and if your up to it, the spike may not be caused by P2P, it might your dish is aligned a little off. I went on my roof and moved my dish and I ended up going up there a total of about 68 times and finally I get 2.0 down and 1.5 up. just a thought.
--
First rule of fiber optics: you do not talk about fiber optics |
|
| Actually the ISP did tests, turning off and on port 1214 (used by Kazaa) and the latency would return to normal, go back up, return to normal. My provider only has a few customers and we are very close to the trasmitter.
When they aren't using P2P I get 20 pings all the time.
--
The democracy will cease to exist when you take away from those who are willing to work and give to those who would not. -Thomas Jefferson |
|
