"Is it my Line" Report Tool

karnallie · Mar 1, 2016

Dodgey Line

Hi Guys,

I think you would all agree that my line is quite shot at the moment?? I had my 2mbps upgraded to 4mbps last week, but since then I noticed my line really is quite slow. I am actually quite sure it was this problematic before the upgrade!

Zertop's LineTool Results
Date/Time: Tue Mar 01 17:45:39 CAT 2016

Basic Report:

Your packet loss was 3%.
Your average ping was 68ms.
Your maximum ping was 119ms.

You seem to have some packet loss. This indicates an issue on the line.
Looking at your average ping, your line seems to be a bit dodgy. This may account for any slow speeds you may be experiencing. However, it could just be related to a high-latency home network (eg... Wi-Fi). If you feel the need, please post the results (at the end of the program) into the forum for advice!

Detailed Report:

Code:

Pinging 169.0.22.1 with 32 bytes of data:
Reply from 169.0.22.1: bytes=32 time=66ms TTL=254
Reply from 169.0.22.1: bytes=32 time=58ms TTL=254
Reply from 169.0.22.1: bytes=32 time=76ms TTL=254
Reply from 169.0.22.1: bytes=32 time=62ms TTL=254
Reply from 169.0.22.1: bytes=32 time=84ms TTL=254
Reply from 169.0.22.1: bytes=32 time=59ms TTL=254
Reply from 169.0.22.1: bytes=32 time=84ms TTL=254
Reply from 169.0.22.1: bytes=32 time=75ms TTL=254
Reply from 169.0.22.1: bytes=32 time=63ms TTL=254
Reply from 169.0.22.1: bytes=32 time=49ms TTL=254
Reply from 169.0.22.1: bytes=32 time=69ms TTL=254
Reply from 169.0.22.1: bytes=32 time=59ms TTL=254
Request timed out.
Reply from 169.0.22.1: bytes=32 time=60ms TTL=254
Reply from 169.0.22.1: bytes=32 time=76ms TTL=254
Reply from 169.0.22.1: bytes=32 time=66ms TTL=254
Reply from 169.0.22.1: bytes=32 time=71ms TTL=254
Reply from 169.0.22.1: bytes=32 time=56ms TTL=254
Reply from 169.0.22.1: bytes=32 time=76ms TTL=254
Reply from 169.0.22.1: bytes=32 time=64ms TTL=254
Reply from 169.0.22.1: bytes=32 time=69ms TTL=254
Reply from 169.0.22.1: bytes=32 time=64ms TTL=254
Reply from 169.0.22.1: bytes=32 time=119ms TTL=254
Reply from 169.0.22.1: bytes=32 time=75ms TTL=254
Reply from 169.0.22.1: bytes=32 time=68ms TTL=254
Reply from 169.0.22.1: bytes=32 time=49ms TTL=254
Reply from 169.0.22.1: bytes=32 time=66ms TTL=254
Reply from 169.0.22.1: bytes=32 time=65ms TTL=254
Reply from 169.0.22.1: bytes=32 time=73ms TTL=254
Reply from 169.0.22.1: bytes=32 time=66ms TTL=254

Ping statistics for 169.0.22.1:
    Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
    Minimum = 49ms, Maximum = 119ms, Average = 68ms

Zertop · Mar 1, 2016

Hey Man!

Line is definitely a bit strange - most probably due to the upgrade!

Have you made sure that the line is correctly syncing at the full 4Mbps? It might be struggling to reach reach and therefore acting slow?

Z

karnallie · Mar 1, 2016

Zertop said:
Hey Man!

Line is definitely a bit strange - most probably due to the upgrade!

Have you made sure that the line is correctly syncing at the full 4Mbps? It might be struggling to reach reach and therefore acting slow?

Z

Hey Zertop,

See my line parameters reported by Billion Bipac 7402 router, so it seems it is syncing at the correct speed:
Upstream - 512000
Downstream - 4096000
SNR Margin(Upstream) - 14 dB
SNR Margin(Downstream) - 18.0 dB
Line Attenuation(Upstream) - 10.5 dB
Line Attenuation(Downstream) - 20.5 dB

The actual connectivity is very much ruined, as you can see from this speed test:

I logged a fault with Telkom this afternoon. I think it is safe to say that was necessary?

BigBear · Mar 1, 2016

Zertop's LineTool Results
Date/Time: Tue Mar 01 21:02:18 CAT 2016

Basic Report:

Your packet loss was 0%.
Your average ping was 86ms.
Your maximum ping was 189ms.

Looking at your average ping, there is definitely something wrong with your line! Please post the results (at the end of the program) into the forum for advice!

Detailed Report:

Code:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=158ms TTL=63
Reply from 155.239.255.250: bytes=32 time=101ms TTL=63
Reply from 155.239.255.250: bytes=32 time=189ms TTL=63
Reply from 155.239.255.250: bytes=32 time=49ms TTL=63
Reply from 155.239.255.250: bytes=32 time=74ms TTL=63
Reply from 155.239.255.250: bytes=32 time=44ms TTL=63
Reply from 155.239.255.250: bytes=32 time=101ms TTL=63
Reply from 155.239.255.250: bytes=32 time=152ms TTL=63
Reply from 155.239.255.250: bytes=32 time=95ms TTL=63
Reply from 155.239.255.250: bytes=32 time=158ms TTL=63
Reply from 155.239.255.250: bytes=32 time=44ms TTL=63
Reply from 155.239.255.250: bytes=32 time=91ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=104ms TTL=63
Reply from 155.239.255.250: bytes=32 time=135ms TTL=63
Reply from 155.239.255.250: bytes=32 time=104ms TTL=63
Reply from 155.239.255.250: bytes=32 time=104ms TTL=63
Reply from 155.239.255.250: bytes=32 time=183ms TTL=63
Reply from 155.239.255.250: bytes=32 time=123ms TTL=63
Reply from 155.239.255.250: bytes=32 time=42ms TTL=63
Reply from 155.239.255.250: bytes=32 time=42ms TTL=63
Reply from 155.239.255.250: bytes=32 time=68ms TTL=63
Reply from 155.239.255.250: bytes=32 time=108ms TTL=63
Reply from 155.239.255.250: bytes=32 time=41ms TTL=63
Reply from 155.239.255.250: bytes=32 time=41ms TTL=63
Reply from 155.239.255.250: bytes=32 time=44ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=41ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=42ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 39ms, Maximum = 189ms, Average = 86ms

Zertop · Mar 2, 2016

LuMiNOuS said:
Hey Zertop,

See my line parameters reported by Billion Bipac 7402 router, so it seems it is syncing at the correct speed:
Upstream - 512000
Downstream - 4096000
SNR Margin(Upstream) - 14 dB
SNR Margin(Downstream) - 18.0 dB
Line Attenuation(Upstream) - 10.5 dB
Line Attenuation(Downstream) - 20.5 dB

The actual connectivity is very much ruined, as you can see from this speed test:
View attachment 346761

I logged a fault with Telkom this afternoon. I think it is safe to say that was necessary?

Yeah, definitely a problem there. That's probably the best course of action! Let me know what they say

Z

Zertop · Mar 2, 2016

BigBear said:

Zertop's LineTool Results
Date/Time: Tue Mar 01 21:02:18 CAT 2016

Basic Report:

Your packet loss was 0%.
Your average ping was 86ms.
Your maximum ping was 189ms.

Looking at your average ping, there is definitely something wrong with your line! Please post the results (at the end of the program) into the forum for advice!

Detailed Report:

Code:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=158ms TTL=63
Reply from 155.239.255.250: bytes=32 time=101ms TTL=63
Reply from 155.239.255.250: bytes=32 time=189ms TTL=63
Reply from 155.239.255.250: bytes=32 time=49ms TTL=63
Reply from 155.239.255.250: bytes=32 time=74ms TTL=63
Reply from 155.239.255.250: bytes=32 time=44ms TTL=63
Reply from 155.239.255.250: bytes=32 time=101ms TTL=63
Reply from 155.239.255.250: bytes=32 time=152ms TTL=63
Reply from 155.239.255.250: bytes=32 time=95ms TTL=63
Reply from 155.239.255.250: bytes=32 time=158ms TTL=63
Reply from 155.239.255.250: bytes=32 time=44ms TTL=63
Reply from 155.239.255.250: bytes=32 time=91ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=104ms TTL=63
Reply from 155.239.255.250: bytes=32 time=135ms TTL=63
Reply from 155.239.255.250: bytes=32 time=104ms TTL=63
Reply from 155.239.255.250: bytes=32 time=104ms TTL=63
Reply from 155.239.255.250: bytes=32 time=183ms TTL=63
Reply from 155.239.255.250: bytes=32 time=123ms TTL=63
Reply from 155.239.255.250: bytes=32 time=42ms TTL=63
Reply from 155.239.255.250: bytes=32 time=42ms TTL=63
Reply from 155.239.255.250: bytes=32 time=68ms TTL=63
Reply from 155.239.255.250: bytes=32 time=108ms TTL=63
Reply from 155.239.255.250: bytes=32 time=41ms TTL=63
Reply from 155.239.255.250: bytes=32 time=41ms TTL=63
Reply from 155.239.255.250: bytes=32 time=44ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=41ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=42ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 39ms, Maximum = 189ms, Average = 86ms

Definitely something wrong there :/

Is it intermittent or constant?

Z

BigBear · Mar 2, 2016

Zertop said:
Definitely something wrong there :/

Is it intermittent or constant?

Z

Constant Disconnects and Speed Dropping

Today

Code:

2016/03/02

16H00

ADSL Configuration
This page shows the setting of the ADSL Router.
Adsl Line Status	SHOWTIME.L0
Adsl Mode	G992.3
Up Stream	767 kbps
Down Stream	7167 kbps
Attenuation Down Stream	28
Attenuation Up Stream	17
SNR Margin Down Stream	11.3
SNR Margin Up Stream	17.2
Vendor ID	RETK
Firmware Version	4926dc02
CRC Errors	827
Up Stream BER	21e-7
Down Stream BER	14e-7
Up Output Power	12
Down Output Power	19.5
Down Stream ES	1293
Up Stream ES	26
Down Stream SES	375
Up Stream SES	9
Down Stream UAS	960
Up Stream UAS	0

Code:

Wed Mar 2 1:8:14 2016	0	system	Port 2 link down
Wed Mar 2 1:8:19 2016	1	system	ppp1: link terminated
Wed Mar 2 1:8:32 2016	2	system	Port 2 link up
Wed Mar 2 1:8:37 2016	3	system	ppp1: link established
Wed Mar 2 1:8:37 2016	4	system	ppp1: IP-up
Wed Mar 2 1:8:37 2016	5	system	ppp1: update DDNS
Wed Mar 2 8:4:57 2016	6	system	Port 2 link down
Wed Mar 2 8:5:2 2016	7	system	ppp1: link terminated
Wed Mar 2 8:6:10 2016	8	system	Port 2 link up
Wed Mar 2 8:6:13 2016	9	system	ppp1: link established
Wed Mar 2 8:6:14 2016	10	system	ppp1: IP-up
Wed Mar 2 8:6:14 2016	11	system	ppp1: update DDNS
Wed Mar 2 9:42:53 2016	12	system	Port 2 link down
Wed Mar 2 9:42:58 2016	13	system	ppp1: link terminated
Wed Mar 2 9:44:10 2016	14	system	Port 2 link up
Wed Mar 2 9:44:14 2016	15	system	ppp1: link established
Wed Mar 2 9:44:14 2016	16	system	ppp1: IP-up
Wed Mar 2 9:44:14 2016	17	system	ppp1: update DDNS
Wed Mar 2 9:57:49 2016	18	system	Port 2 link down
Wed Mar 2 9:57:54 2016	19	system	ppp1: link terminated
Wed Mar 2 9:59:15 2016	20	system	Port 2 link up
Wed Mar 2 9:59:19 2016	21	system	ppp1: link established
Wed Mar 2 9:59:19 2016	22	system	ppp1: IP-up
Wed Mar 2 9:59:19 2016	23	system	ppp1: update DDNS
Wed Mar 2 15:4:41 2016	24	system	Port 2 link down
Wed Mar 2 15:4:46 2016	25	system	ppp1: link terminated
Wed Mar 2 15:5:54 2016	26	system	Port 2 link up
Wed Mar 2 15:5:57 2016	27	system	ppp1: link established
Wed Mar 2 15:5:57 2016	28	system	ppp1: UP
Wed Mar 2 15:5:57 2016	29	system	ppp1: update DDNS
Wed Mar 2 15:59:36 2016	30	other	admin web login successfully.

Yesterday

Code:

2016/03/01

20H42

ADSL Configuration
This page shows the setting of the ADSL Router.
Adsl Line Status	SHOWTIME.L0
Adsl Mode	G992.5
Up Stream	767 kbps
Down Stream	8191 kbps
Attenuation Down Stream	27
Attenuation Up Stream	17
SNR Margin Down Stream	24.1
SNR Margin Up Stream	19.0
Vendor ID	RETK
Firmware Version	4926dc02
CRC Errors	305
Up Stream BER	0e-7
Down Stream BER	3e-7
Up Output Power	12
Down Output Power	20
Down Stream ES	1159
Up Stream ES	0
Down Stream SES	275
Up Stream SES	0
Down Stream UAS	589
Up Stream UAS	0

Code:

Tue Mar 1 1:6:3 2016	0	system	Port 2 link down
Tue Mar 1 1:6:8 2016	1	system	ppp1: link terminated
Tue Mar 1 1:6:22 2016	2	system	Port 2 link up
Tue Mar 1 1:6:24 2016	3	system	ppp1: link established
Tue Mar 1 1:6:25 2016	4	system	ppp1: IP-up
Tue Mar 1 1:6:25 2016	5	system	ppp1: update DDNS
Tue Mar 1 8:47:32 2016	6	system	Port 2 link down
Tue Mar 1 8:47:37 2016	7	system	ppp1: link terminated
Tue Mar 1 8:47:51 2016	8	system	Port 2 link up
Tue Mar 1 8:47:55 2016	9	system	ppp1: link established
Tue Mar 1 8:47:55 2016	10	system	ppp1: IP-up
Tue Mar 1 8:47:55 2016	11	system	ppp1: update DDNS
Tue Mar 1 8:48:26 2016	12	system	Port 2 link down
Tue Mar 1 8:48:31 2016	13	system	ppp1: link terminated
Tue Mar 1 8:48:45 2016	14	system	Port 2 link up
Tue Mar 1 8:48:51 2016	15	system	ppp1: link established
Tue Mar 1 8:48:51 2016	16	system	ppp1: IP-up
Tue Mar 1 8:48:51 2016	17	system	ppp1: update DDNS
Tue Mar 1 12:10:30 2016	18	system	Port 2 link down
Tue Mar 1 12:10:35 2016	19	system	ppp1: link terminated
Tue Mar 1 12:11:42 2016	20	system	Port 2 link up
Tue Mar 1 12:11:46 2016	21	system	ppp1: link established
Tue Mar 1 12:11:46 2016	22	system	ppp1: IP-up
Tue Mar 1 12:11:46 2016	23	system	ppp1: update DDNS
Tue Mar 1 19:28:24 2016	24	system	Port 2 link down
Tue Mar 1 19:28:29 2016	25	system	ppp1: link terminated
Tue Mar 1 19:28:42 2016	26	system	Port 2 link up
Tue Mar 1 19:28:45 2016	27	system	ppp1: link established
Tue Mar 1 19:28:45 2016	28	system	ppp1: IP-up
Tue Mar 1 19:28:45 2016	29	system	ppp1: update DDNS
Tue Mar 1 19:28:53 2016	30	system	Port 2 link down
Tue Mar 1 19:28:58 2016	31	system	ppp1: link terminated
Tue Mar 1 19:29:34 2016	32	system	Port 2 link up
Tue Mar 1 19:29:38 2016	33	system	ppp1: link established
Tue Mar 1 19:29:38 2016	34	system	ppp1: IP-up
Tue Mar 1 19:29:38 2016	35	system	ppp1: update DDNS
Tue Mar 1 20:35:25 2016	36	other	admin web login successfully.
Tue Mar 1 20:41:47 2016	37	other	admin web login successfully.

karnallie · Mar 3, 2016

So apparently Telkom has tested my line and consider the problem fixed. I guess not:

Zertop's LineTool Results
Date/Time: Thu Mar 03 17:38:59 CAT 2016

Basic Report:

Your packet loss was 40%.
Your average ping was 51ms.
Your maximum ping was 116ms.

You have serious packet loss. Please post these results to the forum for advice.

Detailed Report:

Code:

Pinging 169.0.22.1 with 32 bytes of data:
Request timed out.
Reply from 169.0.22.1: bytes=32 time=77ms TTL=254
Reply from 169.0.22.1: bytes=32 time=44ms TTL=254
Reply from 169.0.22.1: bytes=32 time=116ms TTL=254
Reply from 169.0.22.1: bytes=32 time=49ms TTL=254
Reply from 169.0.22.1: bytes=32 time=12ms TTL=254
Request timed out.
Request timed out.
Reply from 169.0.22.1: bytes=32 time=51ms TTL=254
Reply from 169.0.22.1: bytes=32 time=77ms TTL=254
Reply from 169.0.22.1: bytes=32 time=12ms TTL=254
Request timed out.
Reply from 169.0.22.1: bytes=32 time=105ms TTL=254
Reply from 169.0.22.1: bytes=32 time=30ms TTL=254
Request timed out.
Request timed out.
Reply from 169.0.22.1: bytes=32 time=13ms TTL=254
Request timed out.
Request timed out.
Reply from 169.0.22.1: bytes=32 time=85ms TTL=254
Reply from 169.0.22.1: bytes=32 time=12ms TTL=254
Reply from 169.0.22.1: bytes=32 time=101ms TTL=254
Reply from 169.0.22.1: bytes=32 time=29ms TTL=254
Request timed out.
Request timed out.
Reply from 169.0.22.1: bytes=32 time=12ms TTL=254
Reply from 169.0.22.1: bytes=32 time=86ms TTL=254
Reply from 169.0.22.1: bytes=32 time=17ms TTL=254
Request timed out.
Request timed out.

Ping statistics for 169.0.22.1:
    Packets: Sent = 30, Received = 18, Lost = 12 (40% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 116ms, Average = 51ms

atomcrusher · Mar 3, 2016

Zertop's tool results on my Telkom ISP 4Mbps line

Local Tracert

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.123.254
2 * * * Request timed out.
3 14 ms 12 ms 15 ms ipc-1-up.south.dsl.telkomsa.net [105.226.0.6]
4 13 ms 16 ms 14 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]
5 13 ms 13 ms 13 ms blv-pr-02-be200-vl1.net.telkomsa.net [105.226.0.54]
6 13 ms 12 ms 13 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
7 14 ms 14 ms 15 ms optinet.ct1.napafrica.net [196.10.140.145]
8 18 ms 14 ms 15 ms te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1]
9 14 ms 13 ms 13 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
10 54 ms 36 ms 38 ms 196.28.178.66
11 15 ms 14 ms 14 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
12 16 ms 15 ms 15 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
13 16 ms 17 ms 16 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
14 14 ms 14 ms 16 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

International Tracert

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.123.254
2 * * * Request timed out.
3 14 ms 13 ms 15 ms ipc-1-up.south.dsl.telkomsa.net [105.226.0.6]
4 13 ms 12 ms 13 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]
5 13 ms 13 ms 13 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39.45]
6 155 ms 155 ms 155 ms lon-ip-dir-telecity-pos-1-1-0.telkom-ipnet.co.za [196.43.9.50]
7 175 ms 176 ms 175 ms te0-0-2-1.rcr11.b023101-0.lon01.atlas.cogentco.com [149.6.98.73]
8 176 ms 176 ms 177 ms te0-7-0-1.ccr21.lon01.atlas.cogentco.com [130.117.51.138]
9 * 178 ms 182 ms tata.lon01.atlas.cogentco.com [130.117.15.178]
10 * 175 ms 176 ms if-17-2.tcore1.L78-London.as6453.net [80.231.130.129]
11 182 ms 181 ms 183 ms if-25-2.thar1.LY9-London.as6453.net [80.231.130.142]
12 178 ms 178 ms 179 ms 195.219.92.81
13 182 ms 176 ms 173 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
14 179 ms 176 ms 184 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 20.0 megabytes in 1:10 seconds. (290.84 KB/s)

Local Speedtest
Downloaded 15.6 megabytes in 39 seconds. (408.28 KB/s)

Test End Timestamp
2016/03/03 17:57:21.78

Aokiji · Mar 3, 2016

Zertop's LineTool Results
Date/Time: Thu Mar 03 23:49:08 CAT 2016

Basic Report:

Your packet loss was 100%.
Your average ping was 0ms.
Your maximum ping was 0ms.

You have serious packet loss. Please post these results to the forum for advice.

Detailed Report:

Code:

Pinging 41.170.67.97 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 41.170.67.97:
    Packets: Sent = 30, Received = 0, Lost = 30 (100% loss),

Mmmm so what does this mean?

Tracing route to 41.170.67.97 over a maximum of 30 hops

1 1 ms 1 ms <1 ms ZeroToleranceNetwork.home.gateway [10.0.0.1]
2 42 ms 29 ms 33 ms 41.170.67.97
3 * * * Request timed out.
4 38 ms 34 ms 36 ms jhb-in1.ip.adsl.co.za [169.1.5.42]
5 33 ms 32 ms 39 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 35 ms 42 ms 43 ms 169-1-5-74.ip.afrihost.co.za [169.1.5.74]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete

Zertop · Mar 8, 2016

Have you got a line adsl filter installed? That is often the cause for these kinds of symptoms

Z

BigBear said:

Constant Disconnects and Speed Dropping

Today

Code:

2016/03/02

16H00

ADSL Configuration
This page shows the setting of the ADSL Router.
Adsl Line Status	SHOWTIME.L0
Adsl Mode	G992.3
Up Stream	767 kbps
Down Stream	7167 kbps
Attenuation Down Stream	28
Attenuation Up Stream	17
SNR Margin Down Stream	11.3
SNR Margin Up Stream	17.2
Vendor ID	RETK
Firmware Version	4926dc02
CRC Errors	827
Up Stream BER	21e-7
Down Stream BER	14e-7
Up Output Power	12
Down Output Power	19.5
Down Stream ES	1293
Up Stream ES	26
Down Stream SES	375
Up Stream SES	9
Down Stream UAS	960
Up Stream UAS	0

Code:

Wed Mar 2 1:8:14 2016	0	system	Port 2 link down
Wed Mar 2 1:8:19 2016	1	system	ppp1: link terminated
Wed Mar 2 1:8:32 2016	2	system	Port 2 link up
Wed Mar 2 1:8:37 2016	3	system	ppp1: link established
Wed Mar 2 1:8:37 2016	4	system	ppp1: IP-up
Wed Mar 2 1:8:37 2016	5	system	ppp1: update DDNS
Wed Mar 2 8:4:57 2016	6	system	Port 2 link down
Wed Mar 2 8:5:2 2016	7	system	ppp1: link terminated
Wed Mar 2 8:6:10 2016	8	system	Port 2 link up
Wed Mar 2 8:6:13 2016	9	system	ppp1: link established
Wed Mar 2 8:6:14 2016	10	system	ppp1: IP-up
Wed Mar 2 8:6:14 2016	11	system	ppp1: update DDNS
Wed Mar 2 9:42:53 2016	12	system	Port 2 link down
Wed Mar 2 9:42:58 2016	13	system	ppp1: link terminated
Wed Mar 2 9:44:10 2016	14	system	Port 2 link up
Wed Mar 2 9:44:14 2016	15	system	ppp1: link established
Wed Mar 2 9:44:14 2016	16	system	ppp1: IP-up
Wed Mar 2 9:44:14 2016	17	system	ppp1: update DDNS
Wed Mar 2 9:57:49 2016	18	system	Port 2 link down
Wed Mar 2 9:57:54 2016	19	system	ppp1: link terminated
Wed Mar 2 9:59:15 2016	20	system	Port 2 link up
Wed Mar 2 9:59:19 2016	21	system	ppp1: link established
Wed Mar 2 9:59:19 2016	22	system	ppp1: IP-up
Wed Mar 2 9:59:19 2016	23	system	ppp1: update DDNS
Wed Mar 2 15:4:41 2016	24	system	Port 2 link down
Wed Mar 2 15:4:46 2016	25	system	ppp1: link terminated
Wed Mar 2 15:5:54 2016	26	system	Port 2 link up
Wed Mar 2 15:5:57 2016	27	system	ppp1: link established
Wed Mar 2 15:5:57 2016	28	system	ppp1: UP
Wed Mar 2 15:5:57 2016	29	system	ppp1: update DDNS
Wed Mar 2 15:59:36 2016	30	other	admin web login successfully.

Yesterday

Code:

2016/03/01

20H42

ADSL Configuration
This page shows the setting of the ADSL Router.
Adsl Line Status	SHOWTIME.L0
Adsl Mode	G992.5
Up Stream	767 kbps
Down Stream	8191 kbps
Attenuation Down Stream	27
Attenuation Up Stream	17
SNR Margin Down Stream	24.1
SNR Margin Up Stream	19.0
Vendor ID	RETK
Firmware Version	4926dc02
CRC Errors	305
Up Stream BER	0e-7
Down Stream BER	3e-7
Up Output Power	12
Down Output Power	20
Down Stream ES	1159
Up Stream ES	0
Down Stream SES	275
Up Stream SES	0
Down Stream UAS	589
Up Stream UAS	0

Code:

Tue Mar 1 1:6:3 2016	0	system	Port 2 link down
Tue Mar 1 1:6:8 2016	1	system	ppp1: link terminated
Tue Mar 1 1:6:22 2016	2	system	Port 2 link up
Tue Mar 1 1:6:24 2016	3	system	ppp1: link established
Tue Mar 1 1:6:25 2016	4	system	ppp1: IP-up
Tue Mar 1 1:6:25 2016	5	system	ppp1: update DDNS
Tue Mar 1 8:47:32 2016	6	system	Port 2 link down
Tue Mar 1 8:47:37 2016	7	system	ppp1: link terminated
Tue Mar 1 8:47:51 2016	8	system	Port 2 link up
Tue Mar 1 8:47:55 2016	9	system	ppp1: link established
Tue Mar 1 8:47:55 2016	10	system	ppp1: IP-up
Tue Mar 1 8:47:55 2016	11	system	ppp1: update DDNS
Tue Mar 1 8:48:26 2016	12	system	Port 2 link down
Tue Mar 1 8:48:31 2016	13	system	ppp1: link terminated
Tue Mar 1 8:48:45 2016	14	system	Port 2 link up
Tue Mar 1 8:48:51 2016	15	system	ppp1: link established
Tue Mar 1 8:48:51 2016	16	system	ppp1: IP-up
Tue Mar 1 8:48:51 2016	17	system	ppp1: update DDNS
Tue Mar 1 12:10:30 2016	18	system	Port 2 link down
Tue Mar 1 12:10:35 2016	19	system	ppp1: link terminated
Tue Mar 1 12:11:42 2016	20	system	Port 2 link up
Tue Mar 1 12:11:46 2016	21	system	ppp1: link established
Tue Mar 1 12:11:46 2016	22	system	ppp1: IP-up
Tue Mar 1 12:11:46 2016	23	system	ppp1: update DDNS
Tue Mar 1 19:28:24 2016	24	system	Port 2 link down
Tue Mar 1 19:28:29 2016	25	system	ppp1: link terminated
Tue Mar 1 19:28:42 2016	26	system	Port 2 link up
Tue Mar 1 19:28:45 2016	27	system	ppp1: link established
Tue Mar 1 19:28:45 2016	28	system	ppp1: IP-up
Tue Mar 1 19:28:45 2016	29	system	ppp1: update DDNS
Tue Mar 1 19:28:53 2016	30	system	Port 2 link down
Tue Mar 1 19:28:58 2016	31	system	ppp1: link terminated
Tue Mar 1 19:29:34 2016	32	system	Port 2 link up
Tue Mar 1 19:29:38 2016	33	system	ppp1: link established
Tue Mar 1 19:29:38 2016	34	system	ppp1: IP-up
Tue Mar 1 19:29:38 2016	35	system	ppp1: update DDNS
Tue Mar 1 20:35:25 2016	36	other	admin web login successfully.
Tue Mar 1 20:41:47 2016	37	other	admin web login successfully.

Zertop · Mar 8, 2016

Aokiji said:
Zertop's LineTool Results
Date/Time: Thu Mar 03 23:49:08 CAT 2016

Basic Report:

Your packet loss was 100%.
Your average ping was 0ms.
Your maximum ping was 0ms.

You have serious packet loss. Please post these results to the forum for advice.

Detailed Report:

Code:

Pinging 41.170.67.97 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 41.170.67.97: Packets: Sent = 30, Received = 0, Lost = 30 (100% loss),

Mmmm so what does this mean?

Tracing route to 41.170.67.97 over a maximum of 30 hops

1 1 ms 1 ms <1 ms ZeroToleranceNetwork.home.gateway [10.0.0.1]
2 42 ms 29 ms 33 ms 41.170.67.97
3 * * * Request timed out.
4 38 ms 34 ms 36 ms jhb-in1.ip.adsl.co.za [169.1.5.42]
5 33 ms 32 ms 39 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 35 ms 42 ms 43 ms 169-1-5-74.ip.afrihost.co.za [169.1.5.74]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete

That's very strange...

From the trace route, your line is still a bit dodge.

Z

Zertop · Mar 8, 2016

atomcrusher said:
Local Tracert

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.123.254
2 * * * Request timed out.
3 14 ms 12 ms 15 ms ipc-1-up.south.dsl.telkomsa.net [105.226.0.6]
4 13 ms 16 ms 14 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]
5 13 ms 13 ms 13 ms blv-pr-02-be200-vl1.net.telkomsa.net [105.226.0.54]
6 13 ms 12 ms 13 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
7 14 ms 14 ms 15 ms optinet.ct1.napafrica.net [196.10.140.145]
8 18 ms 14 ms 15 ms te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1]
9 14 ms 13 ms 13 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
10 54 ms 36 ms 38 ms 196.28.178.66
11 15 ms 14 ms 14 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
12 16 ms 15 ms 15 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
13 16 ms 17 ms 16 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
14 14 ms 14 ms 16 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

International Tracert

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.123.254
2 * * * Request timed out.
3 14 ms 13 ms 15 ms ipc-1-up.south.dsl.telkomsa.net [105.226.0.6]
4 13 ms 12 ms 13 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]
5 13 ms 13 ms 13 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39.45]
6 155 ms 155 ms 155 ms lon-ip-dir-telecity-pos-1-1-0.telkom-ipnet.co.za [196.43.9.50]
7 175 ms 176 ms 175 ms te0-0-2-1.rcr11.b023101-0.lon01.atlas.cogentco.com [149.6.98.73]
8 176 ms 176 ms 177 ms te0-7-0-1.ccr21.lon01.atlas.cogentco.com [130.117.51.138]
9 * 178 ms 182 ms tata.lon01.atlas.cogentco.com [130.117.15.178]
10 * 175 ms 176 ms if-17-2.tcore1.L78-London.as6453.net [80.231.130.129]
11 182 ms 181 ms 183 ms if-25-2.thar1.LY9-London.as6453.net [80.231.130.142]
12 178 ms 178 ms 179 ms 195.219.92.81
13 182 ms 176 ms 173 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
14 179 ms 176 ms 184 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 20.0 megabytes in 1:10 seconds. (290.84 KB/s)

Local Speedtest
Downloaded 15.6 megabytes in 39 seconds. (408.28 KB/s)

Test End Timestamp
2016/03/03 17:57:21.78

Looks good to me! Depending on linespeed of course

Zertop · Mar 8, 2016

LuMiNOuS said:

So apparently Telkom has tested my line and consider the problem fixed. I guess not:

Zertop's LineTool Results
Date/Time: Thu Mar 03 17:38:59 CAT 2016

Basic Report:

Your packet loss was 40%.
Your average ping was 51ms.
Your maximum ping was 116ms.

You have serious packet loss. Please post these results to the forum for advice.

Detailed Report:

Code:

Pinging 169.0.22.1 with 32 bytes of data:
Request timed out.
Reply from 169.0.22.1: bytes=32 time=77ms TTL=254
Reply from 169.0.22.1: bytes=32 time=44ms TTL=254
Reply from 169.0.22.1: bytes=32 time=116ms TTL=254
Reply from 169.0.22.1: bytes=32 time=49ms TTL=254
Reply from 169.0.22.1: bytes=32 time=12ms TTL=254
Request timed out.
Request timed out.
Reply from 169.0.22.1: bytes=32 time=51ms TTL=254
Reply from 169.0.22.1: bytes=32 time=77ms TTL=254
Reply from 169.0.22.1: bytes=32 time=12ms TTL=254
Request timed out.
Reply from 169.0.22.1: bytes=32 time=105ms TTL=254
Reply from 169.0.22.1: bytes=32 time=30ms TTL=254
Request timed out.
Request timed out.
Reply from 169.0.22.1: bytes=32 time=13ms TTL=254
Request timed out.
Request timed out.
Reply from 169.0.22.1: bytes=32 time=85ms TTL=254
Reply from 169.0.22.1: bytes=32 time=12ms TTL=254
Reply from 169.0.22.1: bytes=32 time=101ms TTL=254
Reply from 169.0.22.1: bytes=32 time=29ms TTL=254
Request timed out.
Request timed out.
Reply from 169.0.22.1: bytes=32 time=12ms TTL=254
Reply from 169.0.22.1: bytes=32 time=86ms TTL=254
Reply from 169.0.22.1: bytes=32 time=17ms TTL=254
Request timed out.
Request timed out.

Ping statistics for 169.0.22.1:
    Packets: Sent = 30, Received = 18, Lost = 12 (40% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 116ms, Average = 51ms

Yeah, definitely not yet fixed...

Have they got back to you since this post?

karnallie · Mar 8, 2016

Zertop said:
Yeah, definitely not yet fixed...

Have they got back to you since this post?

Nope, they have actually not gotten back to me since last week... The logged fault is still shown as "Open" though. I am quite un-amused as my internet is basically useless now

I PM'ed TelkomZA yesterday, but also to no avail thus far.

BigBear · Mar 9, 2016

Zertop said:
Have you got a line adsl filter installed? That is often the cause for these kinds of symptoms

Z

Yup

Telkom Tech came and checked it as well

Still only syncing at 6 mbps

BigBear · Mar 10, 2016

Zertop's LineTool Results
Date/Time: Thu Mar 10 17:50:59 CAT 2016

Basic Report:

Your packet loss was 6%.
Your average ping was 237ms.
Your maximum ping was 394ms.

You seem to have some packet loss. This indicates an issue on the line.
Looking at your average ping, there is definitely something wrong with your line! Please post the results (at the end of the program) into the forum for advice!

Detailed Report:

Code:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=209ms TTL=63
Reply from 155.239.255.250: bytes=32 time=293ms TTL=63
Reply from 155.239.255.250: bytes=32 time=325ms TTL=63
Reply from 155.239.255.250: bytes=32 time=274ms TTL=63
Reply from 155.239.255.250: bytes=32 time=330ms TTL=63
Reply from 155.239.255.250: bytes=32 time=216ms TTL=63
Reply from 155.239.255.250: bytes=32 time=215ms TTL=63
Reply from 155.239.255.250: bytes=32 time=184ms TTL=63
Reply from 155.239.255.250: bytes=32 time=217ms TTL=63
Reply from 155.239.255.250: bytes=32 time=192ms TTL=63
Reply from 155.239.255.250: bytes=32 time=204ms TTL=63
Reply from 155.239.255.250: bytes=32 time=246ms TTL=63
Reply from 155.239.255.250: bytes=32 time=147ms TTL=63
Reply from 155.239.255.250: bytes=32 time=122ms TTL=63
Reply from 155.239.255.250: bytes=32 time=180ms TTL=63
Reply from 155.239.255.250: bytes=32 time=136ms TTL=63
Reply from 155.239.255.250: bytes=32 time=216ms TTL=63
Reply from 155.239.255.250: bytes=32 time=253ms TTL=63
Reply from 155.239.255.250: bytes=32 time=222ms TTL=63
Reply from 155.239.255.250: bytes=32 time=231ms TTL=63
Reply from 155.239.255.250: bytes=32 time=208ms TTL=63
Reply from 155.239.255.250: bytes=32 time=394ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=350ms TTL=63
Reply from 155.239.255.250: bytes=32 time=280ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=394ms TTL=63
Reply from 155.239.255.250: bytes=32 time=169ms TTL=63
Reply from 155.239.255.250: bytes=32 time=218ms TTL=63
Reply from 155.239.255.250: bytes=32 time=213ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
    Minimum = 122ms, Maximum = 394ms, Average = 237ms

Zertop · Mar 11, 2016

LuMiNOuS said:
Nope, they have actually not gotten back to me since last week... The logged fault is still shown as "Open" though. I am quite un-amused as my internet is basically useless now

I PM'ed TelkomZA yesterday, but also to no avail thus far.

Try contacting your local Telkom shop. They usually have a way of assisting faster than the national hotline

Zertop · Mar 12, 2016

BigBear said:
Yup

Telkom Tech came and checked it as well

Still only syncing at 6 mbps

BigBear said:

Zertop's LineTool Results
Date/Time: Thu Mar 10 17:50:59 CAT 2016

Basic Report:

Your packet loss was 6%.
Your average ping was 237ms.
Your maximum ping was 394ms.

You seem to have some packet loss. This indicates an issue on the line.
Looking at your average ping, there is definitely something wrong with your line! Please post the results (at the end of the program) into the forum for advice!

Detailed Report:

Code:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=209ms TTL=63
Reply from 155.239.255.250: bytes=32 time=293ms TTL=63
Reply from 155.239.255.250: bytes=32 time=325ms TTL=63
Reply from 155.239.255.250: bytes=32 time=274ms TTL=63
Reply from 155.239.255.250: bytes=32 time=330ms TTL=63
Reply from 155.239.255.250: bytes=32 time=216ms TTL=63
Reply from 155.239.255.250: bytes=32 time=215ms TTL=63
Reply from 155.239.255.250: bytes=32 time=184ms TTL=63
Reply from 155.239.255.250: bytes=32 time=217ms TTL=63
Reply from 155.239.255.250: bytes=32 time=192ms TTL=63
Reply from 155.239.255.250: bytes=32 time=204ms TTL=63
Reply from 155.239.255.250: bytes=32 time=246ms TTL=63
Reply from 155.239.255.250: bytes=32 time=147ms TTL=63
Reply from 155.239.255.250: bytes=32 time=122ms TTL=63
Reply from 155.239.255.250: bytes=32 time=180ms TTL=63
Reply from 155.239.255.250: bytes=32 time=136ms TTL=63
Reply from 155.239.255.250: bytes=32 time=216ms TTL=63
Reply from 155.239.255.250: bytes=32 time=253ms TTL=63
Reply from 155.239.255.250: bytes=32 time=222ms TTL=63
Reply from 155.239.255.250: bytes=32 time=231ms TTL=63
Reply from 155.239.255.250: bytes=32 time=208ms TTL=63
Reply from 155.239.255.250: bytes=32 time=394ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=350ms TTL=63
Reply from 155.239.255.250: bytes=32 time=280ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=394ms TTL=63
Reply from 155.239.255.250: bytes=32 time=169ms TTL=63
Reply from 155.239.255.250: bytes=32 time=218ms TTL=63
Reply from 155.239.255.250: bytes=32 time=213ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
    Minimum = 122ms, Maximum = 394ms, Average = 237ms

Not great :/

Still as bad?

Z

EchoZA · Mar 12, 2016

My current situation is a borked exchange... 3 weeks ago 10Mb line became 6Mb (max) with bad noise etc. Tech was here today and together we redid every joint going back to the exchange. Still the same, as a last resort connected direct at the cable coming out the DSLAM and the same results...

Join the MyBroadband community

Get started

"Is it my Line" Report Tool

Well-Known Member

Expert Member

Well-Known Member

Expert Member

Expert Member

Expert Member

Expert Member

Well-Known Member

Expert Member

Active Member

Expert Member

Expert Member

Expert Member

Expert Member

Well-Known Member

Expert Member

Expert Member

Expert Member

Expert Member

Expert Member