What is going on here Telkom?

S

Slip

Senior Member
Joined
May 16, 2005
Messages
622
Reaction score
338
So they upgraded the DSLAM in the exchange and after first not being able to authenticate to my ISP (working again) my once stable connection is not so nice. Ran a couple of traceroutes right after one another. Looking at the results does anyone know what this is indicative of? Should I ask to have my port recreated? Modem says I am syncing at 10MB but speed test results are pathetic

Last Result:
Download Speed: 314 kbps (39.3 KB/sec transfer rate)
Upload Speed: 138 kbps (17.3 KB/sec transfer rate)
Latency: 777 ms
30/11/2014 16:55:03

Pinging www.google.com [74.125.233.4] with 32 bytes of data:
Reply from 74.125.233.4: bytes=32 time=2247ms TTL=54
Reply from 74.125.233.4: bytes=32 time=1973ms TTL=54
Reply from 74.125.233.4: bytes=32 time=1855ms TTL=54
Reply from 74.125.233.4: bytes=32 time=2351ms TTL=54
Reply from 74.125.233.4: bytes=32 time=1878ms TTL=54
Reply from 74.125.233.4: bytes=32 time=1922ms TTL=54
Reply from 74.125.233.4: bytes=32 time=15ms TTL=54
Reply from 74.125.233.4: bytes=32 time=11ms TTL=54
Reply from 74.125.233.4: bytes=32 time=16ms TTL=54
Reply from 74.125.233.4: bytes=32 time=12ms TTL=54
Reply from 74.125.233.4: bytes=32 time=9ms TTL=54
Reply from 74.125.233.4: bytes=32 time=11ms TTL=54
Reply from 74.125.233.4: bytes=32 time=663ms TTL=54
Reply from 74.125.233.4: bytes=32 time=948ms TTL=54
Reply from 74.125.233.4: bytes=32 time=1218ms TTL=54
Reply from 74.125.233.4: bytes=32 time=614ms TTL=54
Reply from 74.125.233.4: bytes=32 time=375ms TTL=54
Reply from 74.125.233.4: bytes=32 time=915ms TTL=54
Reply from 74.125.233.4: bytes=32 time=1288ms TTL=54
Reply from 74.125.233.4: bytes=32 time=1326ms TTL=54
Reply from 74.125.233.4: bytes=32 time=1221ms TTL=54
Reply from 74.125.233.4: bytes=32 time=2158ms TTL=54
Reply from 74.125.233.4: bytes=32 time=2037ms TTL=54
Reply from 74.125.233.4: bytes=32 time=1890ms TTL=54
Reply from 74.125.233.4: bytes=32 time=1284ms TTL=54

Tracing route to Telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home [192.168.1.1]
2 1171 ms 952 ms 1048 ms dsl-197-245-122-1.voxdsl.co.za [197.245.122.1]
3 1286 ms 1037 ms 1035 ms 196.41.199.126
4 1201 ms 1044 ms 954 ms 196.41.12.5
5 1130 ms 1079 ms 1084 ms 41.193.32.53
6 1000 ms 1044 ms 1130 ms 41.193.32.78
7 1051 ms 1038 ms 1081 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.252.5]
8 1244 ms 1355 ms 1220 ms 196.43.39.166
9 1157 ms 1210 ms 1081 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
10 1141 ms 1295 ms 1108 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
11 1060 ms 495 ms 27 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43.22.222]

Trace complete.


Tracing route to Telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms home [192.168.1.1]
2 12 ms 8 ms 7 ms dsl-197-245-122-1.voxdsl.co.za [197.245.122.1]
3 47 ms 12 ms 9 ms 196.41.199.126
4 385 ms 58 ms 13 ms 196.41.12.5
5 37 ms 21 ms 20 ms 41.193.32.53
6 21 ms 13 ms 16 ms 41.193.32.78
7 8 ms 8 ms 63 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.252.5]
8 36 ms 26 ms 14 ms 196.43.39.166
9 16 ms 10 ms 11 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
10 12 ms 11 ms 12 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
11 45 ms 14 ms 13 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43.22.222]

Trace complete.

Tracing route to Telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home [192.168.1.1]
2 14 ms 12 ms 15 ms dsl-197-245-122-1.voxdsl.co.za [197.245.122.1]
3 11 ms 9 ms 45 ms 196.41.199.126
4 22 ms 41 ms 11 ms 196.41.12.5
5 393 ms 553 ms 609 ms 41.193.32.53
6 1306 ms 1225 ms 919 ms 41.193.32.78
7 1068 ms 1119 ms 1061 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.252.5]
8 1226 ms 1330 ms 976 ms 196.43.39.166
9 1028 ms 864 ms 1014 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
10 1029 ms 1115 ms 1058 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
11 1288 ms 1098 ms 906 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43.22.222]

Trace complete.


Tracing route to Telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home [192.168.1.1]
2 1318 ms 1099 ms 1229 ms dsl-197-245-122-1.voxdsl.co.za [197.245.122.1]
3 1374 ms 1178 ms 1085 ms 196.41.199.126
4 1144 ms 1236 ms 976 ms 196.41.12.5
5 1066 ms 1020 ms 1025 ms 41.193.32.53
6 822 ms 777 ms 816 ms 41.193.32.78
7 799 ms 35 ms 8 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.252.5]
8 16 ms 10 ms 21 ms 196.43.39.166
9 9 ms 21 ms 13 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
10 16 ms 134 ms 45 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
11 29 ms 23 ms * nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43.22.222]
12 34 ms 17 ms 25 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43.22.222]
 
Jeez, that ping is insane! I wouldn't bother with recreating the port. There may be something wrong with the line.
 
Been having that issue for 2 weeks now....... just restarted my connection and it wont connect again posting this from my phone
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X