Company Forums » Companies beginning with U » Unplugged Internet > Today's pings

Today's pings

With Unplugged Internet

Pinging redirect.gamespy.com [207.38.1.157] with 32 bytes of data:

Reply from 207.38.1.157: bytes=32 time=77ms TTL=51
Reply from 207.38.1.157: bytes=32 time=225ms TTL=51
Reply from 207.38.1.157: bytes=32 time=101ms TTL=51
Reply from 207.38.1.157: bytes=32 time=231ms TTL=51
Reply from 207.38.1.157: bytes=32 time=211ms TTL=51
Reply from 207.38.1.157: bytes=32 time=58ms TTL=51
Reply from 207.38.1.157: bytes=32 time=226ms TTL=51
Reply from 207.38.1.157: bytes=32 time=250ms TTL=51
Reply from 207.38.1.157: bytes=32 time=149ms TTL=51
Reply from 207.38.1.157: bytes=32 time=167ms 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 = 58ms, Maximum = 250ms, Average = 169ms

This is at 8am mind you. Completely unusable and silly that day after day this goes on with no solution, I'm trying to be understanding but the "whole internet" thing erks me. It isn't the whole internet when you have dial up latency and no solution for it.

With Coastinet.com

Pinging redirect.gamespy.com [207.38.1.157] with 32 bytes of data:

Reply from 207.38.1.157: bytes=32 time=38ms TTL=54
Reply from 207.38.1.157: bytes=32 time=94ms TTL=54
Reply from 207.38.1.157: bytes=32 time=38ms TTL=54
Reply from 207.38.1.157: bytes=32 time=48ms TTL=54
Reply from 207.38.1.157: bytes=32 time=45ms TTL=54
Reply from 207.38.1.157: bytes=32 time=38ms TTL=54
Reply from 207.38.1.157: bytes=32 time=74ms TTL=54
Reply from 207.38.1.157: bytes=32 time=36ms TTL=54
Reply from 207.38.1.157: bytes=32 time=55ms TTL=54
Reply from 207.38.1.157: bytes=32 time=36ms TTL=54

Ping statistics for 207.38.1.157:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 94ms, Average = 50ms

With Coastinet.com

Pinging lax.speakeasy.net [64.81.45.2] with 32 bytes of data:

Reply from 64.81.45.2: bytes=32 time=35ms TTL=245
Reply from 64.81.45.2: bytes=32 time=53ms TTL=245
Reply from 64.81.45.2: bytes=32 time=35ms TTL=245
Reply from 64.81.45.2: bytes=32 time=56ms TTL=245
Reply from 64.81.45.2: bytes=32 time=38ms TTL=245
Reply from 64.81.45.2: bytes=32 time=36ms TTL=245
Reply from 64.81.45.2: bytes=32 time=34ms TTL=245
Reply from 64.81.45.2: bytes=32 time=46ms TTL=245
Reply from 64.81.45.2: bytes=32 time=38ms TTL=245
Reply from 64.81.45.2: bytes=32 time=87ms TTL=245

Ping statistics for 64.81.45.2:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 87ms, Average = 45ms

So much for Unplugged selling the whole internet. I guess it's the whole internet plus illegal file trading minus online 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
[text was edited by author 2002-07-13 11:22:17]

Yeah, the only time it seems that I can play games is around 3-4 a.m. This isn't really convenient for me, hehe. I can't really stay up until 3 a.m. every night if I want to play a game of Quake 3 or Counter-strike. When my friends want me to play Counter-strike on the internet with them, I'm all for it (the game is actually kind of fun when you play with people you know). Unfortunately this is usually in the evening or early at night and my pings are usually unplayable. I guess they're going to have to make a choice between the gamers and the P2P users. If they kill off P2P they risk the chance of losing those P2P customers. If they don't though they risk the chance of losing their gamers (like you). With cable right around the corner, I guess they're going to have to make that decision. The gamers will be unhappy with Unplugged's latency if they don't kill P2P and go to AT&T and the P2P guys might be unhappy with no KaZaa (aww, cry me a river you bandwidth hogs) and they might go to AT&T, so who knows. I do know that AT&T in our area really owns for gaming though. A friend of mine that lives off of Ontario has AT&T broadband and he pings 9ms in-game (yes NINE MILLI-SECONDS) on the Counter-strike server we like to play on sometimes. When I have him ping servers in DOS they're always rock-solid and very low. Take for example, lax.speakeasy.net. Last time I had him ping it, he pinged a constant 12ms in DOS and he says that his ping remains rock-solid even during peak hours. The reason I got wireless also was for gaming, I would rather be capped at 16k/sec or so and ping real low and stable then be able to download at 130k/sec but have unplayable ping. That's why I had ISDN, even thought it was way over-priced I always had really stable and low ping. I cancelled it though because I heard Unplugged had real good pings. At first when I got them (around March I believe), my pings were GREAT. I guess this was before all the P2P people signed up with Unplugged. I would maintain a constant 15-20ms ping in game on most California servers, I was in heaven. Then it slowly degraded. I guess it's time for them to make a decision.

"This is at 8am mind you. Completely unusable and silly that day after day this goes on with no solution, I'm trying to be understanding but the "whole internet" thing erks me. It isn't the whole internet when you have dial up latency and no solution for it."

Actually, when I had 56k through Earthlink I had stable 90-100ms ping 24/7.

reply to jca2050
If they don't fix the latency they WILL lose me as a customer.

From Unplugged

Pinging redirect.gamespy.com [207.38.1.157] with 32 bytes of data:

Reply from 207.38.1.157: bytes=32 time=436ms TTL=54
Reply from 207.38.1.157: bytes=32 time=602ms TTL=54
Reply from 207.38.1.157: bytes=32 time=210ms TTL=54
Reply from 207.38.1.157: bytes=32 time=72ms TTL=54
Reply from 207.38.1.157: bytes=32 time=211ms TTL=54
Reply from 207.38.1.157: bytes=32 time=293ms TTL=54
Reply from 207.38.1.157: bytes=32 time=484ms TTL=54
Reply from 207.38.1.157: bytes=32 time=567ms TTL=54
Reply from 207.38.1.157: bytes=32 time=261ms TTL=54
Reply from 207.38.1.157: bytes=32 time=573ms TTL=54

Ping statistics for 207.38.1.157:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 602ms, Average = 370ms

Bitchen I hope they fix it soon, I have always supported their service but they're making it harder and harder to. Come on, help us out here !

From Coastinet

Pinging redirect.gamespy.com [207.38.1.157] with 32 bytes of data:

Reply from 207.38.1.157: bytes=32 time=40ms TTL=54
Reply from 207.38.1.157: bytes=32 time=37ms TTL=54
Reply from 207.38.1.157: bytes=32 time=36ms TTL=54
Reply from 207.38.1.157: bytes=32 time=37ms TTL=54
Reply from 207.38.1.157: bytes=32 time=37ms TTL=54
Reply from 207.38.1.157: bytes=32 time=37ms TTL=54
Reply from 207.38.1.157: bytes=32 time=37ms TTL=54
Reply from 207.38.1.157: bytes=32 time=117ms TTL=54
Reply from 207.38.1.157: bytes=32 time=41ms TTL=54
Reply from 207.38.1.157: bytes=32 time=81ms TTL=54

Ping statistics for 207.38.1.157:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 117ms, Average = 50ms

From Unplugged again

Pinging redirect.gamespy.com [207.38.1.157] with 32 bytes of data:

Reply from 207.38.1.157: bytes=32 time=45ms TTL=51
Reply from 207.38.1.157: bytes=32 time=58ms TTL=51
Reply from 207.38.1.157: bytes=32 time=184ms TTL=51
Reply from 207.38.1.157: bytes=32 time=154ms TTL=51
Reply from 207.38.1.157: bytes=32 time=167ms TTL=51
Reply from 207.38.1.157: bytes=32 time=147ms TTL=51
Reply from 207.38.1.157: bytes=32 time=130ms TTL=51
Reply from 207.38.1.157: bytes=32 time=139ms TTL=51
Reply from 207.38.1.157: bytes=32 time=187ms TTL=51
Reply from 207.38.1.157: bytes=32 time=318ms 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 = 45ms, Maximum = 318ms, Average = 152ms

--
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-14 23:26:20]

Wow, Coastinet seems really stable now, they disabled ports for P2P programs, didn't they?

I don't know. I don't use P2P.

Ah, a friend of mine uses KaZaa quite a bit, he said he can't connect to any P2P services anymore on Coastinet. He doesn't mind though.

There's your answer. Too bad Unplugged can't reach the same conclusion and fix their service.