| 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 | Re: High pings 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
| Re: High pings 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 | |
|
| | | | | Re: High pings 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 | Re: High pings Do you have Quake 3 or Jedi Knight 2 installed? If I run a server can you try and connect to it?  | |
|
| | | | |
| Re: High pings 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
| Re: High pings 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
| Re: High pings 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] | |
|
| | | | | | | | | | Re: High pings I tried connecting but I get parse errors right after connecting. | |
|
| | | | | | | | jca2050Premium
join:2002-02-04
Hacienda Heights, CA | 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. | |
|
| | | | | | | | | | | Re: High pings Oh yeah...hold on. I'm getting it. | |
|
| | | | 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. | |
|
|  guhunaR.I.P MikePremium
join:2001-03-31
Antioch, CA
 ·Covad Communicat..
| 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 | |
|
| | | | Re: High pings 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 | |
|
jca2050Premium
join:2002-02-04
Hacienda Heights, CA Reviews:
·Verizon FiOS
| Game Server? I'm really curious how well Unplugged customers ping to each other in-game. I have a fast linux box (1.2ghz athlon, 512mb ram) that has its own static ip that I can run a few game servers off of, if anyone wants to try. Right now all I have is Quakeworld, Quake 3 and Jedi Knight 2 on it. I can copy whatever is in demand from my main box and set it up. I have Quake 1, Quake 2, Quake 3, Unreal Tournament, Jedi Knight 2, Soldier of Fortune 2, Half-life, Counter-strike, Return to Castle Wolfenstein. You can get a hold of me here, or on AIM (jca2050) or on IRC (irc.enterthegame.com nickname: FienD). | |
|
| | | Re: Game Server? Well, I got 30-50ms to your box but others seems to hang trying to connect. Maybe if the tower can handle the traffic we'll get discounts from choosing the play games inside the network. | |
|
| | | Talked to Duane today...he says traffic inside the network isn't regulated. Hosting games for other Unplugged users doesn't count for priority.
--
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 | |
|
| | jca2050Premium
join:2002-02-04
Hacienda Heights, CA | Re: Game Server? Cool, I'm still not sure which servers to put up. Any ideas? | |
|
| | | | | Re: Game Server? I dunno...it seems that we are the only ones who play. Maybe Unplugged should send out an email to all users or attach something to the billing statement soliciting interest in gaming.
--
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 | |
|
| | High pings caused by P2P Well, Unplugged isn't alone. Along with everyone else they're dealing with the P2P issue like Kazaa's DoS Supernode function. They're working on the problem though and the latency spikes seem to be occurring less and less.
Rumor has it that 3000/3000 service may be coming by the end of summer. Can't wait. | |
|
| | Game Servers People with Unplugged...I just talked to Unplugged today and they're soliciting opinions on whether there is enough interest in Unplugged having their own game servers. What games and how often people play. If you have Unplugged, post if you play with how often, what times, and what game or games you play most.
I play two evenings a week, usually Soldier of Fortune 2, Sum of All Fears and occasionally Team Fortress. | |
|
| Latency improving Latency is improving on Unplugged's network. This is pinging www.mplayer.com I got 2 spikes but 111ms and 130ms spikes aren't bad. The rest are excellent in the 20's. The second set I pulled a few minutes later and added them here. They're a little worse but still I would consider them pretty good.
Pinging redirect.gamespy.com [207.38.1.157] with 32 bytes of data:
Reply from 207.38.1.157: bytes=32 time=26ms TTL=51
Reply from 207.38.1.157: bytes=32 time=61ms TTL=51
Reply from 207.38.1.157: bytes=32 time=22ms TTL=51
Reply from 207.38.1.157: bytes=32 time=22ms TTL=51
Reply from 207.38.1.157: bytes=32 time=56ms TTL=49
Reply from 207.38.1.157: bytes=32 time=111ms TTL=49
Reply from 207.38.1.157: bytes=32 time=22ms TTL=51
Reply from 207.38.1.157: bytes=32 time=23ms TTL=51
Reply from 207.38.1.157: bytes=32 time=37ms TTL=49
Reply from 207.38.1.157: bytes=32 time=130ms TTL=49
Ping statistics for 207.38.1.157:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 130ms, Average = 51ms
Pinging redirect.gamespy.com [207.38.1.157] with 32 bytes of data:
Reply from 207.38.1.157: bytes=32 time=64ms TTL=49
Reply from 207.38.1.157: bytes=32 time=52ms TTL=51
Reply from 207.38.1.157: bytes=32 time=43ms TTL=51
Reply from 207.38.1.157: bytes=32 time=65ms TTL=49
Reply from 207.38.1.157: bytes=32 time=85ms TTL=49
Reply from 207.38.1.157: bytes=32 time=130ms TTL=51
Reply from 207.38.1.157: bytes=32 time=72ms TTL=51
Reply from 207.38.1.157: bytes=32 time=54ms TTL=49
Reply from 207.38.1.157: bytes=32 time=41ms TTL=49
Reply from 207.38.1.157: bytes=32 time=50ms TTL=51
Ping statistics for 207.38.1.157:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 130ms, Average = 65ms
[text was edited by author 2002-07-01 23:55:59] | |
|
| | Gotta love these lamers Trollers are everywhere. I write a favorable review about the service and some douche comes in (turns out for the second time) and lies about the service, manufactures claims...lies about his own service, etc.
It's sad that a lamer like him detracts from what otherwise would be a pleasant forum. My review isn't alone, he went after another review for Unplugged and this type of teen lamer activities pops up in Comcast, TW, and AOL reviews.
It's funny how some lamer in the middle of nowhere...who hasn't tried and can't even get the service comments on the service. It's expected as school is out for summer. They'll put down their Barbies and come in here talking smack.
--
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 | |
|
|
|
| Re: sigh... more lag I'm not having the same lag problems to LA Speakeasy...but I'm having those problems with my office DSL connection...so I'd say it's them...they're taking on more traffic than they can handle. Try San Fran or San Diego when that happens again...I have better time with them. Speakeasy LA is frequently a problem...for me at least whether I use Coastinet, Unplugged or Verizon DSL.
Using Unplugged
Pinging lax.speakeasy.net [64.81.45.2] with 32 bytes of data:
Reply from 64.81.45.2: bytes=32 time=71ms TTL=243
Reply from 64.81.45.2: bytes=32 time=48ms TTL=243
Reply from 64.81.45.2: bytes=32 time=78ms TTL=243
Reply from 64.81.45.2: bytes=32 time=45ms TTL=243
Ping statistics for 64.81.45.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 78ms, Average = 60ms
Using Coastinet
Pinging lax.speakeasy.net [64.81.45.2] with 32 bytes of data:
Reply from 64.81.45.2: bytes=32 time=83ms TTL=244
Reply from 64.81.45.2: bytes=32 time=39ms TTL=244
Reply from 64.81.45.2: bytes=32 time=68ms TTL=244
Reply from 64.81.45.2: bytes=32 time=37ms TTL=244
Ping statistics for 64.81.45.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 83ms, Average = 56ms
[text was edited by author 2002-07-05 16:29:55] | |
|
jca2050Premium
join:2002-02-04
Hacienda Heights, CA | 3mbit? Does anyone know if Unplugged's 3mbit turn-up date is still July 15th/16th? That's what Russell told me but that was 2 1/2 months ago so I don't know if it's changed since then. | |
|
| | | Re: 3mbit? They're working on it...but according to Duane the 3rd parties pretty much follow their own schedule while they try and push them along. July 15th will probably be too soon, but it shouldn't be much longer after that.
--
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 | |
|
jca2050Premium
join:2002-02-04
Hacienda Heights, CA Reviews:
·Verizon FiOS
| ughhh Pinging eof.qwca.net [64.208.50.10] with 32 bytes of data
Reply from 64.208.50.10: bytes=32 time=160ms TTL=246
Reply from 64.208.50.10: bytes=32 time=170ms TTL=246
Reply from 64.208.50.10: bytes=32 time=200ms TTL=246
Reply from 64.208.50.10: bytes=32 time=170ms TTL=246
Getting 170+ ping in-game. So much for 'priority'.
This is what happens when people start downloading, seems like its happening more often. | |
|
| | | Re: ughhh They should kill off P2P like Coastinet did. | |
|
| | | My latency has improved...today at least.
Pinging redirect.gamespy.com [207.38.1.157] with 32 bytes of data:
Reply from 207.38.1.157: bytes=32 time=36ms TTL=50
Reply from 207.38.1.157: bytes=32 time=35ms TTL=50
Reply from 207.38.1.157: bytes=32 time=34ms TTL=50
Reply from 207.38.1.157: bytes=32 time=41ms TTL=50
Reply from 207.38.1.157: bytes=32 time=36ms TTL=50
Reply from 207.38.1.157: bytes=32 time=38ms TTL=50
Reply from 207.38.1.157: bytes=32 time=37ms TTL=50
Reply from 207.38.1.157: bytes=32 time=37ms TTL=50
Reply from 207.38.1.157: bytes=32 time=37ms TTL=50
Reply from 207.38.1.157: bytes=32 time=38ms TTL=50
Ping statistics for 207.38.1.157:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 41ms, Average = 36ms
Pinging lax.speakeasy.net [64.81.45.2] with 32 bytes of data:
Reply from 64.81.45.2: bytes=32 time=30ms TTL=247
Reply from 64.81.45.2: bytes=32 time=34ms TTL=247
Reply from 64.81.45.2: bytes=32 time=36ms TTL=247
Reply from 64.81.45.2: bytes=32 time=31ms TTL=247
Reply from 64.81.45.2: bytes=32 time=30ms TTL=247
Reply from 64.81.45.2: bytes=32 time=32ms TTL=247
Reply from 64.81.45.2: bytes=32 time=33ms TTL=247
Reply from 64.81.45.2: bytes=32 time=35ms TTL=247
Reply from 64.81.45.2: bytes=32 time=32ms TTL=247
Reply from 64.81.45.2: bytes=32 time=33ms TTL=247
Ping statistics for 64.81.45.2:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 36ms, Average = 32ms
Maybe it's time of day.
--
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 | |
|
| | jca2050Premium
join:2002-02-04
Hacienda Heights, CA Reviews:
·Verizon FiOS
| Re: ughhh Pinging lax.speakeasy.net [64.81.45.2] with 32 bytes of data:
Reply from 64.81.45.2: bytes=32 time=160ms TTL=245
Reply from 64.81.45.2: bytes=32 time=40ms TTL=245
Reply from 64.81.45.2: bytes=32 time=150ms TTL=245
Reply from 64.81.45.2: bytes=32 time=120ms TTL=245
Reply from 64.81.45.2: bytes=32 time=181ms TTL=245
Request timed out.
Reply from 64.81.45.2: bytes=32 time=160ms TTL=245
Reply from 64.81.45.2: bytes=32 time=161ms TTL=245
This is at 12:45am, hehe. I guess it was just that time of the day when no one was owning the connect via P2P. | |
|
jca2050Premium
join:2002-02-04
Hacienda Heights, CA Reviews:
·Verizon FiOS
| P2P I talked to Russell about it, he said they aren't going to kill it, they believe that they sell the whole internet, which makes sense. They said there only problem they have left is the latency. Unfortunately I think the only solution to the latency probably is either more bandwidth or killing P2P, or both.
A friend of mine got me to play CS for a little while today, although I couldn't play for very long...
»www.qwplayers.org/~fiend/ping.jpg
Good game P2P. | |
|
|
| Re: P2P There is no solution to the latency issue if they can't kill supernode. The problem is the powered by parents baggy pant types with their heads in their bungs can't figure out how to turn it off.
1000ms latency is inexcusable though (Wireless Rocks, LOL). They may be trying to sell the whole internet but gaming on their network sucks to the point that you can't do it unless you happen to be on at the exact right time. The reason I have wireless is for gaming. With sat I got 3 times the speed just the bad latency...but I expected it from satellite. I've been pretty understanding in defending Unplugged but my patience is wearing thin, especially at $70 per month. I don't know if I can go another month having to rebalance my router to 100% Coastinet every time I want to game. Seems like a rediculous thing to have to put up with especially when they are aware of the problem and getting complaints. Bad latency 1 time, okay, a few times alright, but now it's been a couple of weeks, sometimes good latency, usually in the afternoon, sometimes horrid unplayable latency in the evening. I mean, look at your connection, 1,000ms, even my satellite was better than that. There comes a time when the ISP needs to take into account what is causing the latency...illegal file theft via P2P, caused by 1 or 2 users, killing the service for other gamers. And the latency doesn't affect just games, WWW page requests are impacted too. You have 500ms-1s latency on the network and you're back to surfing performance not much better than dial up. What's the point on getting pages .7 sec sooner if it takes that much longer with the request 'cause some lamer is acting DNS for the MP3 file theft community.
--
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
[text was edited by author 2002-07-12 19:55:24] | |
|
| Today's pings Recent pings have been decent but the spikes are really bad.
--
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
[text was edited by author 2002-07-12 19:42:49] | |
|
|
See 8 replies to this post |
|
jca2050Premium
join:2002-02-04
Hacienda Heights, CA Reviews:
·Verizon FiOS
| Not bad.. Pinging redirect.gamespy.com [207.38.1.157] with 32 bytes of data:
Reply from 207.38.1.157: bytes=32 time=29ms TTL=52
Reply from 207.38.1.157: bytes=32 time=18ms TTL=52
Reply from 207.38.1.157: bytes=32 time=21ms TTL=52
Reply from 207.38.1.157: bytes=32 time=31ms TTL=52
Reply from 207.38.1.157: bytes=32 time=25ms TTL=52
Reply from 207.38.1.157: bytes=32 time=20ms TTL=52
Reply from 207.38.1.157: bytes=32 time=22ms TTL=52
Reply from 207.38.1.157: bytes=32 time=29ms TTL=52
Reply from 207.38.1.157: bytes=32 time=33ms TTL=52
Reply from 207.38.1.157: bytes=32 time=47ms TTL=52
Ping statistics for 207.38.1.157:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 47ms, Average = 27ms
It looks like things are getting a bit better, hopefully it stays this way. | |
|
| jca2050Premium
join:2002-02-04
Hacienda Heights, CA Reviews:
·Verizon FiOS
| Re: Not bad.. Hmm, this was about 5 mins after the last ping-times.
Pinging redirect.gamespy.com [207.38.1.157] with 32 bytes of data:
Reply from 207.38.1.157: bytes=32 time=40ms TTL=52
Reply from 207.38.1.157: bytes=32 time=19ms TTL=52
Reply from 207.38.1.157: bytes=32 time=94ms TTL=52
Reply from 207.38.1.157: bytes=32 time=37ms TTL=52
Reply from 207.38.1.157: bytes=32 time=343ms TTL=52
Reply from 207.38.1.157: bytes=32 time=77ms TTL=52
Reply from 207.38.1.157: bytes=32 time=107ms TTL=52
Reply from 207.38.1.157: bytes=32 time=85ms TTL=52
Reply from 207.38.1.157: bytes=32 time=110ms TTL=52
Reply from 207.38.1.157: bytes=32 time=20ms TTL=52
Ping statistics for 207.38.1.157:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 343ms, Average = 93ms
As low as 19ms, boy I wish it was stable. | |
|
| | jca2050Premium
join:2002-02-04
Hacienda Heights, CA Reviews:
·Verizon FiOS
| Re: Not bad.. Just tried to play Counter-strike.... nope.
Pinging redirect.gamespy.com [207.38.1.157] with 32 bytes of data:
Reply from 207.38.1.157: bytes=32 time=193ms TTL=52
Reply from 207.38.1.157: bytes=32 time=115ms TTL=52
Reply from 207.38.1.157: bytes=32 time=180ms TTL=52
Reply from 207.38.1.157: bytes=32 time=168ms TTL=52
Ping statistics for 207.38.1.157:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 115ms, Maximum = 193ms, Average = 164ms | |
|
jca2050Premium
join:2002-02-04
Hacienda Heights, CA | Speed test today Your download speed : 367149 bps, or 367 kbps.
A 44.8 KB/sec transfer rate.
Your upload speed : 208333 bps, or 208 kbps.
| |
|
|
See 13 replies to this post |
|
| | Jefe' Post yer speed tests to DSLR speed boards Is it just a 1 time occurance, or does it happen all the time. | |
|
| jca2050Premium
join:2002-02-04
Hacienda Heights, CA | Re: Jefe' Post yer speed tests to DSLR speed boards I can't run speed tests anymore, the speed tests use a java applet and like I said in my pmsg I can't load java applets. | |
|
| | | | Re: Jefe' Post yer speed tests to DSLR speed boards You need to WinXP cached pages patch. You can get it from speedguide.net | |
|
jca2050Premium
join:2002-02-04
Hacienda Heights, CA Reviews:
·Verizon FiOS
| No more Unplugged.. Duane and Russell came today to disconnect my service since I'm moving in 2 days. I can say overall my experience was good. The only problem of course was the latency at times. I was talking with Russ and he told me they are going to experiment with the new 5.8ghz spectrum to improve latency as well as overall performance. They are also going to do the 3mbit upgrade so it looks like their latency will improve quite a bit, best of luck to them on all of that. If I had any problems they were quick to correct them so I would say the tech support is top notch. Russ is even hosting my mail server for me until I get a new one setup at my new location, that in my eyes is a sign of great customer service and commitment. Oh man I had to plug my old modem back in.. I cringed at the tones the modem makes when it connects to the ISP, oh the memories! Oh and seeing that dial-up icon in my taskbar.. ahhh!
[text was edited by author 2002-07-18 21:01:14] | |
|
| | | Re: No more Unplugged.. Well, changing the freq is only going to be a temp solution as the P2P dorks will be moved to 5.8 eventually. The increased BW isn't going to do anything for in-network latency. My ping problems are to THEIR router. Getting an OC48 isn't going to solve that problem.
Latency isn't just an issue for unplugged. All shared networks are having the problems. Cable providers especially as 1000 homes on a node isn't uncommon. Supernode is a problem that needs to be directly addressed, not band-aided.
--
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 | |
|
|
|
