"Is it my Line" Report Tool

Yuu · Apr 9, 2015

Zertop said:
Doesn't look too bad!

Z

Agree, now have a look at my edit

.

Feature Request: A perform another test button please

Zertop · Apr 9, 2015

electrofreeze said:
got it working but cant view the text file only the bottom option works

I'll have to launch a VM to try it. Could you please PM me your version of OSX.

Thanks
Z

Zertop · Apr 9, 2015

Yuu said:
Agree, now have a look at my edit .

Feature Request: A perform another test button please

Sure

electrofreeze · Apr 14, 2015

did you try it on the mac

Drifter · Apr 14, 2015

App hanging at Pinging Telkom Equipment.

Zertop · Apr 14, 2015

electrofreeze said:
did you try it on the mac

I have, but have been unable to recreate the error -_-

Z

Zertop · Apr 14, 2015

Drifter said:
App hanging at Pinging Telkom Equipment.

Which OS are you operating on?

Z

Storeman · Apr 20, 2015

My line is actually working fine. What is the issue here??

Zertop's "Is it my Line" Results
Date/Time: Mon Apr 20 16:09:18 CAT 2015

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 155.239.255.250 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 155.239.255.250:
    Packets: Sent = 30, Received = 0, Lost = 30 (100% loss),

Zertop · Apr 20, 2015

Storeman said:
My line is actually working fine. What is the issue here??

Zertop's "Is it my Line" Results
Date/Time: Mon Apr 20 16:09:18 CAT 2015

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 155.239.255.250 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 155.239.255.250: Packets: Sent = 30, Received = 0, Lost = 30 (100% loss),

You are still running on the old exchange service - so it wont work :/

I'll be updating it soon with a method that allows both old and new equipment.

Z

Foxhound5366 · Apr 20, 2015

Zertop, could you please look at introducing some sort of progress indicator, or a message to flag if the pinging stage is taking too long?

Right now it's just sitting on 'Running tests...' for more than a minute, and I don't know if I should just let it keep running, or give it up as blocked by Telkom?

EDIT: Yup, same as above. Request timed out.

BigBear · Apr 22, 2015

Request timed out Pinging 155.239.255.250

Zertop's "Is it my Line" Results
Date/Time: Wed Apr 22 10:36:34 CAT 2015

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 155.239.255.250 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 155.239.255.250:
    Packets: Sent = 30, Received = 0, Lost = 30 (100% loss),

KingLv · Apr 22, 2015

Big problems...

Zertop's "Is it my Line" Results
Date/Time: Wed Apr 22 23:01:14 CAT 2015

Basic Report:

Your packet loss was 80%.
Your average ping was 451ms.
Your maximum ping was 2566ms.

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

Detailed Report:

Pinging 155.239.255.250 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=2566ms TTL=63
Reply from 155.239.255.250: bytes=32 time=77ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
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 155.239.255.250:
Packets: Sent = 30, Received = 6, Lost = 24 (80% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 2566ms, Average = 451ms

michnieuwoudt · Apr 29, 2015

Soutrivier Exchange Congestion is getting ugly.

Any suggestions?

Thx,
M

Zertop's "Is it my Line" Results
Date/Time: Wed Apr 29 06:29:11 SAST 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 632ms.
Your maximum ping was 799ms.

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:

PING 155.239.255.250 (155.239.255.250): 56 data bytes
64 bytes from 155.239.255.250: icmp_seq=0 ttl=63 time=667.399 ms
64 bytes from 155.239.255.250: icmp_seq=1 ttl=63 time=668.134 ms
64 bytes from 155.239.255.250: icmp_seq=2 ttl=63 time=695.904 ms
64 bytes from 155.239.255.250: icmp_seq=3 ttl=63 time=799.994 ms
64 bytes from 155.239.255.250: icmp_seq=4 ttl=63 time=697.317 ms
64 bytes from 155.239.255.250: icmp_seq=5 ttl=63 time=608.519 ms
64 bytes from 155.239.255.250: icmp_seq=6 ttl=63 time=664.511 ms
64 bytes from 155.239.255.250: icmp_seq=7 ttl=63 time=689.516 ms
64 bytes from 155.239.255.250: icmp_seq=8 ttl=63 time=653.252 ms
64 bytes from 155.239.255.250: icmp_seq=9 ttl=63 time=571.200 ms
64 bytes from 155.239.255.250: icmp_seq=10 ttl=63 time=592.874 ms
64 bytes from 155.239.255.250: icmp_seq=11 ttl=63 time=610.393 ms
64 bytes from 155.239.255.250: icmp_seq=12 ttl=63 time=634.540 ms
64 bytes from 155.239.255.250: icmp_seq=13 ttl=63 time=662.521 ms
64 bytes from 155.239.255.250: icmp_seq=14 ttl=63 time=580.436 ms
64 bytes from 155.239.255.250: icmp_seq=15 ttl=63 time=550.083 ms
64 bytes from 155.239.255.250: icmp_seq=16 ttl=63 time=589.369 ms
64 bytes from 155.239.255.250: icmp_seq=17 ttl=63 time=627.724 ms
64 bytes from 155.239.255.250: icmp_seq=18 ttl=63 time=629.924 ms
64 bytes from 155.239.255.250: icmp_seq=19 ttl=63 time=583.910 ms
64 bytes from 155.239.255.250: icmp_seq=20 ttl=63 time=574.984 ms
64 bytes from 155.239.255.250: icmp_seq=21 ttl=63 time=619.410 ms
64 bytes from 155.239.255.250: icmp_seq=22 ttl=63 time=594.015 ms
64 bytes from 155.239.255.250: icmp_seq=23 ttl=63 time=629.735 ms
64 bytes from 155.239.255.250: icmp_seq=24 ttl=63 time=697.019 ms
64 bytes from 155.239.255.250: icmp_seq=25 ttl=63 time=642.310 ms
64 bytes from 155.239.255.250: icmp_seq=26 ttl=63 time=549.088 ms
64 bytes from 155.239.255.250: icmp_seq=27 ttl=63 time=573.093 ms
64 bytes from 155.239.255.250: icmp_seq=28 ttl=63 time=608.332 ms
64 bytes from 155.239.255.250: icmp_seq=29 ttl=63 time=697.437 ms

--- 155.239.255.250 ping statistics ---
30 packets transmitted, 30 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 549.088/632.098/799.994/54.476 ms

Flashgear · May 8, 2015

Zertop's "Is it my Line" Results
Basic Report:
Your packet loss was 3 percent.
Your average ping was 546ms.
Your maximum ping was 714ms.

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

Detailed Report
Ping results to local Telkom equipment (all on Telkom's equipment)

Pinging 41.183.6.1 with 32 bytes of data:
Reply from 41.183.6.1: bytes=32 time=588ms TTL=254
Reply from 41.183.6.1: bytes=32 time=528ms TTL=254
Reply from 41.183.6.1: bytes=32 time=579ms TTL=254
Reply from 41.183.6.1: bytes=32 time=611ms TTL=254
Reply from 41.183.6.1: bytes=32 time=520ms TTL=254
Reply from 41.183.6.1: bytes=32 time=611ms TTL=254
Reply from 41.183.6.1: bytes=32 time=462ms TTL=254
Reply from 41.183.6.1: bytes=32 time=580ms TTL=254
Reply from 41.183.6.1: bytes=32 time=714ms TTL=254
Reply from 41.183.6.1: bytes=32 time=662ms TTL=254
Reply from 41.183.6.1: bytes=32 time=471ms TTL=254
Reply from 41.183.6.1: bytes=32 time=470ms TTL=254
Reply from 41.183.6.1: bytes=32 time=540ms TTL=254
Reply from 41.183.6.1: bytes=32 time=416ms TTL=254
Reply from 41.183.6.1: bytes=32 time=479ms TTL=254
Reply from 41.183.6.1: bytes=32 time=454ms TTL=254
Reply from 41.183.6.1: bytes=32 time=512ms TTL=254
Reply from 41.183.6.1: bytes=32 time=631ms TTL=254
Reply from 41.183.6.1: bytes=32 time=630ms TTL=254
Reply from 41.183.6.1: bytes=32 time=670ms TTL=254
Reply from 41.183.6.1: bytes=32 time=515ms TTL=254
Reply from 41.183.6.1: bytes=32 time=420ms TTL=254
Reply from 41.183.6.1: bytes=32 time=504ms TTL=254
Reply from 41.183.6.1: bytes=32 time=624ms TTL=254
Reply from 41.183.6.1: bytes=32 time=488ms TTL=254
Reply from 41.183.6.1: bytes=32 time=369ms TTL=254
Reply from 41.183.6.1: bytes=32 time=614ms TTL=254
Request timed out.
Reply from 41.183.6.1: bytes=32 time=626ms TTL=254
Reply from 41.183.6.1: bytes=32 time=554ms TTL=254

Ping statistics for 41.183.6.1:
Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 369ms, Maximum = 714ms, Average = 546ms

Fri 05/08/2015 18:32:02.90

BigBear · May 9, 2015

Zertop's "Is it my Line" Results
Date/Time: Sat May 09 08:36:04 CAT 2015

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 155.239.255.250 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 155.239.255.250:
    Packets: Sent = 30, Received = 0, Lost = 30 (100% loss),

Hmm Not liking my Line..

Manual Tests:

C:\Users>tracert www.mweb.co.za

Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms
2 9 ms 9 ms 9 ms 41-133-92-1.dsl.mweb.co.za [41.133.92.1]
3 11 ms 11 ms 10 ms 197-80-96-138.jhb.mweb.co.za [197.80.96.138]
4 11 ms 10 ms 11 ms vl-92-vic-hscore-1.mweb.co.za [197.80.2.1]
5 299 ms 252 ms 32 ms tengig-0-0-0-2-11-vic-p-1.mweb.co.za [197.80.5.2
25]
6 34 ms 29 ms 31 ms tengig-0-0-0-0-cpt-p-2.mweb.co.za [197.84.4.46]

7 30 ms 29 ms 30 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
8 31 ms 29 ms 29 ms 196.28.178.66
9 67 ms 29 ms 35 ms cte-core-sw2.vwol.net [196.41.144.35]
10 30 ms 36 ms 32 ms www.mweb.co.za [196.2.63.110]

Trace complete.

C:\Users>ping 155.239.255.250

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

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

C:\Users>tracert 155.239.255.250

Tracing route to 155.239.255.250 over a maximum of 30 hops

1 1 ms <1 ms <1 ms
2 10 ms 10 ms 8 ms 41-133-92-1.dsl.mweb.co.za [41.133.92.1]
3 10 ms 9 ms 10 ms 197-80-96-138.jhb.mweb.co.za [197.80.96.138]
4 11 ms 12 ms 10 ms vl-92-vic-hscore-1.mweb.co.za [197.80.2.1]
5 12 ms 14 ms 16 ms tengig-0-0-0-2-11-vic-p-1.mweb.co.za [197.80.5.2
25]
6 11 ms 11 ms 10 ms 197-80-7-5.jhb.mweb.co.za [197.80.7.5]
7 11 ms 21 ms 11 ms jhb.telkom-ipnet.co.za [197.80.4.117]
8 12 ms 10 ms 10 ms rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za [
196.43.25.137]
9 196.43.26.106 reports: Destination host unreachable.

Trace complete.

C:\Users>tracert www.google.co.za

Tracing route to www.google.co.za [216.58.223.3]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms
2 9 ms 10 ms 8 ms 41-133-92-1.dsl.mweb.co.za [41.133.92.1]
3 10 ms 10 ms 10 ms 197-80-96-186.jhb.mweb.co.za [197.80.96.186]
4 11 ms 11 ms 10 ms vl-92-vic-hscore-1.mweb.co.za [197.80.2.1]
5 15 ms 14 ms 14 ms tengig-0-0-0-2-11-vic-p-1.mweb.co.za [197.80.5.2
25]
6 12 ms 11 ms 10 ms 197-80-7-5.jhb.mweb.co.za [197.80.7.5]
7 12 ms 11 ms 11 ms 197-80-96-6.jhb.mweb.co.za [197.80.96.6]
8 17 ms 12 ms 12 ms 72.14.237.239
9 40 ms 11 ms 10 ms jnb01s07-in-f3.1e100.net [216.58.223.3]

Trace complete.

C:\Users>tracert www.google.com

Tracing route to www.google.com [216.58.223.4]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms
2 9 ms 8 ms 8 ms 41-133-92-1.dsl.mweb.co.za [41.133.92.1]
3 10 ms 11 ms 10 ms 197-80-96-186.jhb.mweb.co.za [197.80.96.186]
4 11 ms 11 ms 10 ms vl-92-vic-hscore-2.mweb.co.za [197.80.2.2]
5 12 ms 14 ms 26 ms tengig-0-7-0-2-12-vic-p-1.mweb.co.za [197.80.5.2
41]
6 109 ms 62 ms 44 ms 197-80-7-5.jhb.mweb.co.za [197.80.7.5]
7 80 ms 22 ms 11 ms 197-80-96-6.jhb.mweb.co.za [197.80.96.6]
8 12 ms 12 ms 12 ms 72.14.237.239
9 11 ms 11 ms 12 ms jnb01s07-in-f4.1e100.net [216.58.223.4]

Trace complete.

C:\Users>tracert www.google.co.uk

Tracing route to www.google.co.uk [216.58.223.3]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms
2 11 ms 10 ms 9 ms 41-133-92-1.dsl.mweb.co.za [41.133.92.1]
3 11 ms 12 ms 11 ms 197-80-96-186.jhb.mweb.co.za [197.80.96.186]
4 11 ms 11 ms 10 ms vl-92-vic-hscore-1.mweb.co.za [197.80.2.1]
5 14 ms 14 ms 14 ms tengig-0-0-0-2-11-vic-p-1.mweb.co.za [197.80.5.2
25]
6 11 ms 11 ms 10 ms 197-80-7-5.jhb.mweb.co.za [197.80.7.5]
7 11 ms 10 ms 11 ms 197-80-96-6.jhb.mweb.co.za [197.80.96.6]
8 11 ms 12 ms 11 ms 72.14.237.239
9 12 ms 12 ms 11 ms jnb01s07-in-f3.1e100.net [216.58.223.3]

Trace complete.

ghostR · May 9, 2015

BigBear said:
Zertop's "Is it my Line" Results
Date/Time: Sat May 09 08:36:04 CAT 2015

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 155.239.255.250 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 155.239.255.250: Packets: Sent = 30, Received = 0, Lost = 30 (100% loss),

Hmm Not liking my Line..

Manual Tests:

C:\Users>tracert www.mweb.co.za

Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms
2 9 ms 9 ms 9 ms 41-133-92-1.dsl.mweb.co.za [41.133.92.1]
3 11 ms 11 ms 10 ms 197-80-96-138.jhb.mweb.co.za [197.80.96.138]
4 11 ms 10 ms 11 ms vl-92-vic-hscore-1.mweb.co.za [197.80.2.1]
5 299 ms 252 ms 32 ms tengig-0-0-0-2-11-vic-p-1.mweb.co.za [197.80.5.2
25]
6 34 ms 29 ms 31 ms tengig-0-0-0-0-cpt-p-2.mweb.co.za [197.84.4.46]

7 30 ms 29 ms 30 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
8 31 ms 29 ms 29 ms 196.28.178.66
9 67 ms 29 ms 35 ms cte-core-sw2.vwol.net [196.41.144.35]
10 30 ms 36 ms 32 ms www.mweb.co.za [196.2.63.110]

Trace complete.

C:\Users>ping 155.239.255.250

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

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

C:\Users>tracert 155.239.255.250

Tracing route to 155.239.255.250 over a maximum of 30 hops

1 1 ms <1 ms <1 ms
2 10 ms 10 ms 8 ms 41-133-92-1.dsl.mweb.co.za [41.133.92.1]
3 10 ms 9 ms 10 ms 197-80-96-138.jhb.mweb.co.za [197.80.96.138]
4 11 ms 12 ms 10 ms vl-92-vic-hscore-1.mweb.co.za [197.80.2.1]
5 12 ms 14 ms 16 ms tengig-0-0-0-2-11-vic-p-1.mweb.co.za [197.80.5.2
25]
6 11 ms 11 ms 10 ms 197-80-7-5.jhb.mweb.co.za [197.80.7.5]
7 11 ms 21 ms 11 ms jhb.telkom-ipnet.co.za [197.80.4.117]
8 12 ms 10 ms 10 ms rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za [
196.43.25.137]
9 196.43.26.106 reports: Destination host unreachable.

Trace complete.

C:\Users>tracert www.google.co.za

Tracing route to www.google.co.za [216.58.223.3]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms
2 9 ms 10 ms 8 ms 41-133-92-1.dsl.mweb.co.za [41.133.92.1]
3 10 ms 10 ms 10 ms 197-80-96-186.jhb.mweb.co.za [197.80.96.186]
4 11 ms 11 ms 10 ms vl-92-vic-hscore-1.mweb.co.za [197.80.2.1]
5 15 ms 14 ms 14 ms tengig-0-0-0-2-11-vic-p-1.mweb.co.za [197.80.5.2
25]
6 12 ms 11 ms 10 ms 197-80-7-5.jhb.mweb.co.za [197.80.7.5]
7 12 ms 11 ms 11 ms 197-80-96-6.jhb.mweb.co.za [197.80.96.6]
8 17 ms 12 ms 12 ms 72.14.237.239
9 40 ms 11 ms 10 ms jnb01s07-in-f3.1e100.net [216.58.223.3]

Trace complete.

C:\Users>tracert www.google.com

Tracing route to www.google.com [216.58.223.4]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms
2 9 ms 8 ms 8 ms 41-133-92-1.dsl.mweb.co.za [41.133.92.1]
3 10 ms 11 ms 10 ms 197-80-96-186.jhb.mweb.co.za [197.80.96.186]
4 11 ms 11 ms 10 ms vl-92-vic-hscore-2.mweb.co.za [197.80.2.2]
5 12 ms 14 ms 26 ms tengig-0-7-0-2-12-vic-p-1.mweb.co.za [197.80.5.2
41]
6 109 ms 62 ms 44 ms 197-80-7-5.jhb.mweb.co.za [197.80.7.5]
7 80 ms 22 ms 11 ms 197-80-96-6.jhb.mweb.co.za [197.80.96.6]
8 12 ms 12 ms 12 ms 72.14.237.239
9 11 ms 11 ms 12 ms jnb01s07-in-f4.1e100.net [216.58.223.4]

Trace complete.

C:\Users>tracert www.google.co.uk

Tracing route to www.google.co.uk [216.58.223.3]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms
2 11 ms 10 ms 9 ms 41-133-92-1.dsl.mweb.co.za [41.133.92.1]
3 11 ms 12 ms 11 ms 197-80-96-186.jhb.mweb.co.za [197.80.96.186]
4 11 ms 11 ms 10 ms vl-92-vic-hscore-1.mweb.co.za [197.80.2.1]
5 14 ms 14 ms 14 ms tengig-0-0-0-2-11-vic-p-1.mweb.co.za [197.80.5.2
25]
6 11 ms 11 ms 10 ms 197-80-7-5.jhb.mweb.co.za [197.80.7.5]
7 11 ms 10 ms 11 ms 197-80-96-6.jhb.mweb.co.za [197.80.96.6]
8 11 ms 12 ms 11 ms 72.14.237.239
9 12 ms 12 ms 11 ms jnb01s07-in-f3.1e100.net [216.58.223.3]

Trace complete.

It looks like telkom have not disabled ICMP at your exchange yet.

blaaislaai · May 17, 2015

Zertop's "Is it my Line" Results
Date/Time: Sun May 17 12:44:30 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 74ms.
Your maximum ping was 96ms.

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 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=92ms TTL=63
Reply from 155.239.255.250: bytes=32 time=93ms TTL=63
Reply from 155.239.255.250: bytes=32 time=96ms TTL=63
Reply from 155.239.255.250: bytes=32 time=52ms TTL=63
Reply from 155.239.255.250: bytes=32 time=95ms TTL=63
Reply from 155.239.255.250: bytes=32 time=77ms TTL=63
Reply from 155.239.255.250: bytes=32 time=84ms TTL=63
Reply from 155.239.255.250: bytes=32 time=81ms TTL=63
Reply from 155.239.255.250: bytes=32 time=78ms TTL=63
Reply from 155.239.255.250: bytes=32 time=82ms TTL=63
Reply from 155.239.255.250: bytes=32 time=95ms TTL=63
Reply from 155.239.255.250: bytes=32 time=77ms TTL=63
Reply from 155.239.255.250: bytes=32 time=90ms TTL=63
Reply from 155.239.255.250: bytes=32 time=55ms TTL=63
Reply from 155.239.255.250: bytes=32 time=69ms TTL=63
Reply from 155.239.255.250: bytes=32 time=52ms TTL=63
Reply from 155.239.255.250: bytes=32 time=55ms TTL=63
Reply from 155.239.255.250: bytes=32 time=86ms TTL=63
Reply from 155.239.255.250: bytes=32 time=70ms TTL=63
Reply from 155.239.255.250: bytes=32 time=83ms TTL=63
Reply from 155.239.255.250: bytes=32 time=89ms TTL=63
Reply from 155.239.255.250: bytes=32 time=55ms TTL=63
Reply from 155.239.255.250: bytes=32 time=60ms TTL=63
Reply from 155.239.255.250: bytes=32 time=74ms TTL=63
Reply from 155.239.255.250: bytes=32 time=86ms TTL=63
Reply from 155.239.255.250: bytes=32 time=96ms TTL=63
Reply from 155.239.255.250: bytes=32 time=49ms TTL=63
Reply from 155.239.255.250: bytes=32 time=60ms TTL=63
Reply from 155.239.255.250: bytes=32 time=47ms TTL=63
Reply from 155.239.255.250: bytes=32 time=59ms 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 = 47ms, Maximum = 96ms, Average = 74ms

Tracert always skips the 2nd hop, regardless of ISP.

and my online gaming latency (local) is 100ms average, line congested? I had it installed 1 month ago

Zertop · May 17, 2015

blaaislaai said:

Zertop's "Is it my Line" Results
Date/Time: Sun May 17 12:44:30 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 74ms.
Your maximum ping was 96ms.

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 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=92ms TTL=63
Reply from 155.239.255.250: bytes=32 time=93ms TTL=63
Reply from 155.239.255.250: bytes=32 time=96ms TTL=63
Reply from 155.239.255.250: bytes=32 time=52ms TTL=63
Reply from 155.239.255.250: bytes=32 time=95ms TTL=63
Reply from 155.239.255.250: bytes=32 time=77ms TTL=63
Reply from 155.239.255.250: bytes=32 time=84ms TTL=63
Reply from 155.239.255.250: bytes=32 time=81ms TTL=63
Reply from 155.239.255.250: bytes=32 time=78ms TTL=63
Reply from 155.239.255.250: bytes=32 time=82ms TTL=63
Reply from 155.239.255.250: bytes=32 time=95ms TTL=63
Reply from 155.239.255.250: bytes=32 time=77ms TTL=63
Reply from 155.239.255.250: bytes=32 time=90ms TTL=63
Reply from 155.239.255.250: bytes=32 time=55ms TTL=63
Reply from 155.239.255.250: bytes=32 time=69ms TTL=63
Reply from 155.239.255.250: bytes=32 time=52ms TTL=63
Reply from 155.239.255.250: bytes=32 time=55ms TTL=63
Reply from 155.239.255.250: bytes=32 time=86ms TTL=63
Reply from 155.239.255.250: bytes=32 time=70ms TTL=63
Reply from 155.239.255.250: bytes=32 time=83ms TTL=63
Reply from 155.239.255.250: bytes=32 time=89ms TTL=63
Reply from 155.239.255.250: bytes=32 time=55ms TTL=63
Reply from 155.239.255.250: bytes=32 time=60ms TTL=63
Reply from 155.239.255.250: bytes=32 time=74ms TTL=63
Reply from 155.239.255.250: bytes=32 time=86ms TTL=63
Reply from 155.239.255.250: bytes=32 time=96ms TTL=63
Reply from 155.239.255.250: bytes=32 time=49ms TTL=63
Reply from 155.239.255.250: bytes=32 time=60ms TTL=63
Reply from 155.239.255.250: bytes=32 time=47ms TTL=63
Reply from 155.239.255.250: bytes=32 time=59ms 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 = 47ms, Maximum = 96ms, Average = 74ms

Tracert always skips the 2nd hop, regardless of ISP.

and my online gaming latency (local) is 100ms average, line congested? I had it installed 1 month ago

It does look congested - however it is fairly consistent. Have you asked Telkom to reset the port?

Z

HunterGR · May 17, 2015

Zertop's "Is it my Line" Results
Date/Time: Sun May 17 13:18:26 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 838ms.
Your maximum ping was 1341ms.

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=939ms TTL=63
Reply from 155.239.255.250: bytes=32 time=644ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1051ms TTL=63
Reply from 155.239.255.250: bytes=32 time=659ms TTL=63
Reply from 155.239.255.250: bytes=32 time=920ms TTL=63
Reply from 155.239.255.250: bytes=32 time=920ms TTL=63
Reply from 155.239.255.250: bytes=32 time=869ms TTL=63
Reply from 155.239.255.250: bytes=32 time=820ms TTL=63
Reply from 155.239.255.250: bytes=32 time=784ms TTL=63
Reply from 155.239.255.250: bytes=32 time=795ms TTL=63
Reply from 155.239.255.250: bytes=32 time=797ms TTL=63
Reply from 155.239.255.250: bytes=32 time=781ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1057ms TTL=63
Reply from 155.239.255.250: bytes=32 time=962ms TTL=63
Reply from 155.239.255.250: bytes=32 time=878ms TTL=63
Reply from 155.239.255.250: bytes=32 time=808ms TTL=63
Reply from 155.239.255.250: bytes=32 time=754ms TTL=63
Reply from 155.239.255.250: bytes=32 time=887ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1341ms TTL=63
Reply from 155.239.255.250: bytes=32 time=776ms TTL=63
Reply from 155.239.255.250: bytes=32 time=756ms TTL=63
Reply from 155.239.255.250: bytes=32 time=720ms TTL=63
Reply from 155.239.255.250: bytes=32 time=735ms TTL=63
Reply from 155.239.255.250: bytes=32 time=672ms TTL=63
Reply from 155.239.255.250: bytes=32 time=620ms TTL=63
Reply from 155.239.255.250: bytes=32 time=887ms TTL=63
Reply from 155.239.255.250: bytes=32 time=868ms TTL=63
Reply from 155.239.255.250: bytes=32 time=861ms TTL=63
Reply from 155.239.255.250: bytes=32 time=822ms TTL=63
Reply from 155.239.255.250: bytes=32 time=771ms 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 = 620ms, Maximum = 1341ms, Average = 838ms

Zertop · May 17, 2015

HunterGR said:

Zertop's "Is it my Line" Results
Date/Time: Sun May 17 13:18:26 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 838ms.
Your maximum ping was 1341ms.

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=939ms TTL=63
Reply from 155.239.255.250: bytes=32 time=644ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1051ms TTL=63
Reply from 155.239.255.250: bytes=32 time=659ms TTL=63
Reply from 155.239.255.250: bytes=32 time=920ms TTL=63
Reply from 155.239.255.250: bytes=32 time=920ms TTL=63
Reply from 155.239.255.250: bytes=32 time=869ms TTL=63
Reply from 155.239.255.250: bytes=32 time=820ms TTL=63
Reply from 155.239.255.250: bytes=32 time=784ms TTL=63
Reply from 155.239.255.250: bytes=32 time=795ms TTL=63
Reply from 155.239.255.250: bytes=32 time=797ms TTL=63
Reply from 155.239.255.250: bytes=32 time=781ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1057ms TTL=63
Reply from 155.239.255.250: bytes=32 time=962ms TTL=63
Reply from 155.239.255.250: bytes=32 time=878ms TTL=63
Reply from 155.239.255.250: bytes=32 time=808ms TTL=63
Reply from 155.239.255.250: bytes=32 time=754ms TTL=63
Reply from 155.239.255.250: bytes=32 time=887ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1341ms TTL=63
Reply from 155.239.255.250: bytes=32 time=776ms TTL=63
Reply from 155.239.255.250: bytes=32 time=756ms TTL=63
Reply from 155.239.255.250: bytes=32 time=720ms TTL=63
Reply from 155.239.255.250: bytes=32 time=735ms TTL=63
Reply from 155.239.255.250: bytes=32 time=672ms TTL=63
Reply from 155.239.255.250: bytes=32 time=620ms TTL=63
Reply from 155.239.255.250: bytes=32 time=887ms TTL=63
Reply from 155.239.255.250: bytes=32 time=868ms TTL=63
Reply from 155.239.255.250: bytes=32 time=861ms TTL=63
Reply from 155.239.255.250: bytes=32 time=822ms TTL=63
Reply from 155.239.255.250: bytes=32 time=771ms 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 = 620ms, Maximum = 1341ms, Average = 838ms

Yeah thats just not good at all. Definitely a line fault.

Z

Join the MyBroadband community

Get started

"Is it my Line" Report Tool

Executive Member

Expert Member

Expert Member

Expert Member

Honorary Master

Expert Member

Expert Member

New Member

Expert Member

Honorary Master

Expert Member

Senior Member

New Member

Flashgear

Expert Member

Executive Member

Executive Member

Expert Member

Expert Member

Expert Member