Company Forums » Companies beginning with L » Lightning Bolt DSL > pings gone bad !

pings gone bad !

The first question I have for you, is why are you not using your correct authentication info? AKA, why do you not have the IP address which we have assigned to your circuit?

As far as latency, I don't see any problem with the trace routes you posted, I see a jump when going from Miami to LA, which is normal, and then from Miami, to DC, again, normal.
--
Lightning Bolt Technologies

reply to pimpdeez9
LBDSL,

I have to agree with the poster that the MIA to DC latency is a little high. I can understand the 70+ to L.A. but not to D.C.

I just did a traceroute from my Comcast to the first hop IP listed and it seems Level 3 is having some issues.

Target Name: h-66-166-242-129.miatflad.covad.net
IP: 66.166.242.129
Date/Time: 10/3/2005 9:59:31 PM to 10/3/2005 9:59:42 PM

Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 11 0 0.0 0 0 0 fw.ropeguru.com [192.168.1.99]
2 12 0 0.0 5 10 6 [10.226.144.1]
3 12 0 0.0 6 9 7 [68.86.175.109]
4 12 0 0.0 5 24 7 [68.86.172.94]
5 12 0 0.0 6 11 7 [68.86.172.134]
6 12 0 0.0 8 32 20 [12.124.234.113]
7 12 0 0.0 10 100 29 [12.123.9.62]
8 12 0 0.0 11 32 22 [12.122.80.222]
9 12 0 0.0 12 34 22 att-gw.washdc.level3.net [192.205.32.42]
10 12 0 0.0 11 33 20 ae-2-56.bbr2.Washington1.Level3.net [4.68.121.161]
11 7 0 0.0 106 229 132 as-1-0.mp2.Miami1.Level3.net [64.159.0.2]
12 2 0 0.0 108 129 118 ge-10-1.hsa1.Miami1.Level3.net [64.159.1.98]
13 12 0 0.0 108 123 115 unknown.Level3.net [63.209.147.150]
14 12 0 0.0 103 123 114 h-66-166-242-129.miatflad.covad.net [66.166.242.129]

Look between hops 10 and 11. Just from 20 to 132.
--
FWD#: 223611

reply to pimpdeez9
I agree a 50ms hop from Miami, to DC isn't perfect, but by no means is it anything to worry about.

Now a few hundred ms jump, then yes, but 50ms is more then acceptable.
--
Lightning Bolt Technologies

reply to pimpdeez9
i maybe be a complainer, hehe, but i know my connection after 2 years on covad lines

to atlanta

1 14 ms 15 ms 15 ms h-66-166-242-129.miatflad.covad.net [66.166.242.
129]
2 16 ms 15 ms 15 ms 192.168.11.121
3 16 ms 15 ms 16 ms gigabitethernet5-2-155.hsa1.mia1.bbnplanet.net [
63.209.147.149]
4 17 ms 16 ms 16 ms ge-6-1-0.mp1.Miami1.Level3.net [64.159.1.89]
5 64 ms 63 ms 63 ms ae-0-0.bbr2.Atlanta1.Level3.net [64.159.1.46]
6 65 ms 63 ms 63 ms ge-11-1.hsa2.Atlanta1.Level3.net [4.68.103.101]

7 64 ms 65 ms 62 ms unknown.Level3.net [63.210.88.154]
8 62 ms 62 ms 62 ms games1.atl1.speakeasy.net [216.27.175.6]

just noting my ping should be 30 AT THE MOST. i know theres a problem, i just dont know where it is

Your IP Is 66.166.242.168

My IP is reading as the correct 1, i dont know why the wrong IP is coming out, maybe thats the problem? It just hurts when u figure in the packets being sent through a game and ur ping jumps to 90

First lets work on your IP address, check what you are using to authenticate on our network, you can post here, or PM me, or e-mail our support team, (support at LBTech dot com)

What user name are you using to authenticate?
--
Lightning Bolt Technologies

reply to pimpdeez9
k sent a private msg =)

reply to pimpdeez9
Just an update, LBDSl was nice enough to have a NOC look into the problem since there might be 1 =)

reply to pimpdeez9
I also agree with the poster. 76 ms is way too high to the east coast from florida. Most people don't care about latency, but if someone is using their connection for gaming latency means a lot! Ping really matters, and anyone who's played a game like quake 3, for example, knows that a 76ms ping feels like complete crap...especially when compared with 30 ping. Shit, 50 ms ping feels like crap compared to 20 ms ping. I personally don't think 70 ping is acceptable going from florida to the east coast. However, your ping might not be LB's fault at all (I'm sure you know that).