Ridiculous Latency?

K

Kasyx

Expert Member
Joined
Jun 6, 2006
Messages
2,565
Reaction score
1
Location
127.0.0.1
I recently decided to get myself a Linode box (Dallas Datacenter), however I can't seem to ssh in as I just get timeout errors. I have been messing around with my router settings, wondering if maybe the firewall was up, and that's not it. So I decided to do some pinging and tracerouting. What I discovered horrified me:

(This is a traceroute to my Linode box)
Code: 
 1  * * *
 2  dsl-146-0-01.telkomadsl.co.za (41.146.0.1)  1801.551 ms  2067.145 ms  2113.221 ms
 3  196.43.21.226 (196.43.21.226)  2508.003 ms  1989.953 ms  2905.088 ms
 4  196.43.10.130 (196.43.10.130)  2494.541 ms  1279.600 ms  1731.378 ms
 5  196.43.33.5 (196.43.33.5)  2199.353 ms  1885.746 ms  1883.038 ms
 6  ams-ip-dir-globalc-pos-4-0-1.telkom-ipnet.co.za (196.43.18.38)  2284.223 ms  1440.995 ms  1276.347 ms
 7  212.72.45.225 (212.72.45.225)  1243.380 ms  1849.134 ms  2103.241 ms
 8  ae-33-51.ebr1.Amsterdam1.Level3.net (4.69.139.129)  2753.678 ms  2144.722 ms  1994.140 ms
 9  ae-46-46.ebr2.Dusseldorf1.Level3.net (4.69.143.202)  2074.464 ms ae-45-45.ebr2.Dusseldorf1.Level3.net (4.69.143.198)  1706.655 ms ae-46-46.ebr2.Dusseldorf1.Level3.net (4.69.143.202)  1866.866 ms
10  ae-1-100.ebr1.Dusseldorf1.Level3.net (4.69.141.149)  2544.139 ms  2933.249 ms  2458.879 ms
11  ae-45-45.ebr2.Frankfurt1.Level3.net (4.69.143.166)  1903.546 ms ae-47-47.ebr2.Frankfurt1.Level3.net (4.69.143.174)  2087.657 ms  1423.996 ms
12  ae-42-42.ebr2.Washington1.Level3.net (4.69.137.54)  1443.705 ms  1979.637 ms ae-44-44.ebr2.Washington1.Level3.net (4.69.137.62)  2191.069 ms
13  ae-82-82.csw3.Washington1.Level3.net (4.69.134.154)  3399.029 ms ae-62-62.csw1.Washington1.Level3.net (4.69.134.146)  1703.153 ms ae-82-82.csw3.Washington1.Level3.net (4.69.134.154)  1480.100 ms
14  ae-81-81.ebr1.Washington1.Level3.net (4.69.134.137)  1643.065 ms ae-61-61.ebr1.Washington1.Level3.net (4.69.134.129)  3600.438 ms ae-91-91.ebr1.Washington1.Level3.net (4.69.134.141)  2759.370 ms
15  ae-2-2.ebr3.Atlanta2.Level3.net (4.69.132.85)  2444.354 ms  2275.816 ms *
16  * ae-7-7.ebr3.Dallas1.Level3.net (4.69.134.21)  2075.121 ms  1468.969 ms
17  ae-2-70.edge4.Dallas3.Level3.net (4.69.145.77)  1700.253 ms  1335.059 ms  1116.130 ms
18  THE-PLANET.edge4.Dallas3.Level3.net (4.59.32.30)  1944.421 ms  2481.380 ms  1828.606 ms
19  26.ff.5746.static.theplanet.com (70.87.255.38)  1992.405 ms 2e.ff.5746.static.theplanet.com (70.87.255.46)  1375.519 ms te9-2.dsr01.dllstx3.theplanet.com (70.87.253.14)  2395.467 ms
20  * 46.ff.5746.static.theplanet.com (70.87.255.70)  1505.824 ms *
21  56.ff.5746.static.theplanet.com (70.87.255.86)  1470.912 ms  1589.062 ms 52.ff.5746.static.theplanet.com (70.87.255.82)  2079.897 ms
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Look at those ping response times! 2113.221 ms to the SECOND HOP? What the hell, Telkom?

Trying to ping the IP itself is absolutely futile:

Code: 
[kasyx@apollo ~]$ ping 173.255.199.180
PING 173.255.199.180 (173.255.199.180) 56(84) bytes of data.

--- 173.255.199.180 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9008ms

I honestly have no idea what is going on here, and it isn't just to Linode, check out this ping to Google:

Code: 
PING google.co.za (165.165.38.147) 56(84) bytes of data.
64 bytes from 165.165.38.147: icmp_seq=1 ttl=60 time=1593 ms
64 bytes from 165.165.38.147: icmp_seq=2 ttl=60 time=1388 ms
64 bytes from 165.165.38.147: icmp_seq=3 ttl=60 time=671 ms

--- google.co.za ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 16450ms
rtt min/avg/max/mdev = 671.006/1217.918/1593.984/395.696 ms, pipe 2

As for my line info:

ADSL 384
Telkom Internet
SNR Margin 40.6 DOWN 12.0 UP
Line Attenuation 43.9 DOWN 23.0 UP
033-3969
Lincoln Meade, Pietermaritzburg

Does anyone have any idea what is going on here? I can't survive with latency so bad my ping response from Google is over 1000ms.
 
well i dont see a ping from the router in 1st hop so try ping the router so we can see if the router/lan cable etc. isnt as fault
 
The router responds to direct ping immediately with a "normal" latency. I have completely ruled out anything within my house (to the best of my knowledge)
 
If you run a tracert to a location destination do you receive the same results?
Might be exchange or DSLAM related unfortunately, hop 2 is your first "reply point" with 1800ms+ :(

First step would be to contact Telkom and see if they can reset your port. If that doesn't do the trick you'll have to log a line fault with them. This is of course if you have your line rental and data with Telkom directly and not another ISP.
 
I am with Telkom, unfortunately...

I will contact them, but I doubt they are going to know what I am talking about when I start to tell them about my "ping response times"...
 
they wont fix it if its congestion problem look at Mr.Jax topic hes been trying to get it fixed for months :P
 
Kasyx said:
I am with Telkom, unfortunately...

I will contact them, but I doubt they are going to know what I am talking about when I start to tell them about my "ping response times"...
Click to expand...

Start off the the port recreation as a first step. Take it from there :)
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X