Company Forums » Companies beginning with U » Unplugged Internet > Speed test today

Speed test today

I didn't get a chance to do the pings last night, but your speed tests have my royally pissed...unless you've gone over your 10GB for the month. Is that possible? Then a 400kbps throttle isn't so bad. But if you aren't being throttled...bad latency...crap speeds...makes you wonder why you're paying $70/mo. Looks like Unplugged is getting a little big for their britches.

Just to make you happy

Pings with VerizonDSL

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

Reply from 64.81.45.2: bytes=32 time=31ms TTL=247
Reply from 64.81.45.2: bytes=32 time=34ms TTL=247
Reply from 64.81.45.2: bytes=32 time=34ms TTL=247
Reply from 64.81.45.2: bytes=32 time=31ms TTL=247
Reply from 64.81.45.2: bytes=32 time=32ms TTL=247
Reply from 64.81.45.2: bytes=32 time=35ms 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=31ms TTL=247
Reply from 64.81.45.2: bytes=32 time=32ms 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 = 35ms, Average = 32ms

And its the same, day or night. Gotta love that DSL.
--
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

reply to jca2050
I doubt I went over my 10gb cap, I have hardly downloaded anything the past month. Although I have left my internet radio streams going sometimes, maybe it added up.

reply to jca2050
Also, I was told I would be notified well in advance if I'm coming close to my 10gb cap, as well as if I have gone over it. I haven't received any notifications so I don't think I have. Yes DSL owns for pings. I'm getting cable AND dsl after I move, I can't wait. Whenever a friend of mine and I go play a game, he always brags about his pings. He has AT&T cable in Corona, he always copies and pastes pings from DOS that are sub 20s and never spiking, I hate it!!
[text was edited by author 2002-07-17 21:17:55]

What are you going to use to load balance the Cable & DSL connections?

Well I'll probably use the DSL for myself and let my family use the cable, if there's a certain server I want to play on or need to play on (for a match or whatever) then I'll probably use the cable if it pings better.

You should get a load balacing router like the Nexland Pro800Turbo.

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

Reply from 207.38.1.157: bytes=32 time=17ms TTL=51
Reply from 207.38.1.157: bytes=32 time=15ms TTL=51
Reply from 207.38.1.157: bytes=32 time=16ms TTL=51
Reply from 207.38.1.157: bytes=32 time=17ms TTL=51
Reply from 207.38.1.157: bytes=32 time=17ms TTL=51
Reply from 207.38.1.157: bytes=32 time=16ms TTL=51
Reply from 207.38.1.157: bytes=32 time=15ms TTL=51
Reply from 207.38.1.157: bytes=32 time=16ms TTL=51
Reply from 207.38.1.157: bytes=32 time=16ms TTL=51
Reply from 207.38.1.157: bytes=32 time=16ms TTL=51

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

Reply from 64.81.45.2: bytes=32 time=16ms TTL=243
Reply from 64.81.45.2: bytes=32 time=17ms TTL=243
Reply from 64.81.45.2: bytes=32 time=17ms TTL=243
Reply from 64.81.45.2: bytes=32 time=17ms TTL=243
Reply from 64.81.45.2: bytes=32 time=16ms TTL=243
Reply from 64.81.45.2: bytes=32 time=17ms TTL=243
Reply from 64.81.45.2: bytes=32 time=18ms TTL=243
Reply from 64.81.45.2: bytes=32 time=17ms TTL=243
Reply from 64.81.45.2: bytes=32 time=17ms TTL=243
Reply from 64.81.45.2: bytes=32 time=18ms TTL=243

Your download speed : 1488112 bps, or 1488 kbps.
A 181.6 KB/sec transfer rate.
Your upload speed : 367872 bps, or 367 kbps.
Seems like broadband .. above the 1mbit barrier!

This is how it is all day and night, I love Charter cable.

reply to jca2050
Here's another server I play at called Earthquake.

Pinging 209.179.21.4 with 32 bytes of data:

Reply from 209.179.21.4: bytes=32 time=14ms TTL=241
Reply from 209.179.21.4: bytes=32 time=15ms TTL=241
Reply from 209.179.21.4: bytes=32 time=14ms TTL=241
Reply from 209.179.21.4: bytes=32 time=13ms TTL=241

Ping statistics for 209.179.21.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 15ms, Average = 14ms

reply to jca2050
Here's some ping-times to a bunch of the various Speakeasy POPs...

Speakeasy Los Angeles:

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

Reply from 64.81.45.2: bytes=32 time=14ms TTL=246
Reply from 64.81.45.2: bytes=32 time=14ms TTL=246
Reply from 64.81.45.2: bytes=32 time=15ms TTL=246
Reply from 64.81.45.2: bytes=32 time=16ms TTL=246

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

Speakeasy San Francisco:

Pinging sfo.speakeasy.net [64.81.79.2] with 32 bytes of data:

Reply from 64.81.79.2: bytes=32 time=22ms TTL=240
Reply from 64.81.79.2: bytes=32 time=22ms TTL=240
Reply from 64.81.79.2: bytes=32 time=23ms TTL=240
Reply from 64.81.79.2: bytes=32 time=23ms TTL=240

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

Speakeasy Seattle:

Pinging sea.speakeasy.net [216.231.41.22] with 32 bytes of data:

Reply from 216.231.41.22: bytes=32 time=36ms TTL=240
Reply from 216.231.41.22: bytes=32 time=38ms TTL=240
Reply from 216.231.41.22: bytes=32 time=37ms TTL=240
Reply from 216.231.41.22: bytes=32 time=37ms TTL=240

Ping statistics for 216.231.41.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 38ms, Average = 37ms

Speakeasy Dallas-Fort Worth:

Pinging dfw.speakeasy.net [64.81.127.2] with 32 bytes of data:

Reply from 64.81.127.2: bytes=32 time=42ms TTL=242
Reply from 64.81.127.2: bytes=32 time=39ms TTL=242
Reply from 64.81.127.2: bytes=32 time=40ms TTL=242
Reply from 64.81.127.2: bytes=32 time=40ms TTL=242

Ping statistics for 64.81.127.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 42ms, Average = 40ms

Speakeasy Denver:

Pinging den.speakeasy.net [64.81.111.2] with 32 bytes of data:

Reply from 64.81.111.2: bytes=32 time=47ms TTL=242
Reply from 64.81.111.2: bytes=32 time=46ms TTL=242
Reply from 64.81.111.2: bytes=32 time=47ms TTL=242
Reply from 64.81.111.2: bytes=32 time=48ms TTL=242

Ping statistics for 64.81.111.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 48ms, Average = 47ms

Speakeasy Chicago:

Pinging chi.speakeasy.net [64.81.159.2] with 32 bytes of data:

Reply from 64.81.159.2: bytes=32 time=62ms TTL=240
Reply from 64.81.159.2: bytes=32 time=61ms TTL=240
Reply from 64.81.159.2: bytes=32 time=61ms TTL=240
Reply from 64.81.159.2: bytes=32 time=61ms TTL=240

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

Speakeasy New York:

Pinging nyc.speakeasy.net [216.254.95.2] with 32 bytes of data:

Reply from 216.254.95.2: bytes=32 time=81ms TTL=239
Reply from 216.254.95.2: bytes=32 time=80ms TTL=239
Reply from 216.254.95.2: bytes=32 time=82ms TTL=239
Reply from 216.254.95.2: bytes=32 time=81ms TTL=239

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

Speakeasy Washington DC:

Pinging wdc.speakeasy.net [66.92.159.2] with 32 bytes of data:

Reply from 66.92.159.2: bytes=32 time=72ms TTL=239
Reply from 66.92.159.2: bytes=32 time=74ms TTL=239
Reply from 66.92.159.2: bytes=32 time=73ms TTL=239
Reply from 66.92.159.2: bytes=32 time=74ms TTL=239

Ping statistics for 66.92.159.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 74ms, Average = 73ms
[text was edited by author 2002-07-27 01:37:30]

reply to jca2050
DSL Extreme called today and confirmed the turn-on date for 8/01 but from what I've read the line is usually activate 4-5 days prior so I'll try it when I get the self-install kit/modem in the mail (should be tomorrow). I'll update with pings on it if yea want.
[text was edited by author 2002-07-27 01:41:23]

reply to jca2050
Yeah and that dumbass Hiroshima said there's no such thing as a 14 ping to a game server.

I'm so jealous ya sonavabitch.

Post the ping tests when you get DSL.
--
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

reply to jca2050
What service are you signing up for? Don't they offer a 7100 service? A couple of Benjamins...but damn, 7100!

reply to jca2050
The highest they offer for PacBell is 6mbit but I can't afford $200/month for it.... yet