"Is it my Line" Report Tool

Basjohn said:
Brilliant tool to help see where the blame REALLY sits, considering how Telkom will blame the ISP and the ISP will blame Telkom in and endless cycle.

I'd really suggest a sticky for this one, the other tool is insightful, but this one is very very useful in diagnosis locally.

[EDIT] My only suggestion would be to print the line about the fault being with the ISP in the results.txt, it would make things easier when fussing it out with tech support bottom tier drones.
Click to expand...

Thanks man! I will implement that in the next version :-)

Z
 
atomcrusher said:
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

Pinging 105.224.92.1 with 32 bytes of data:
Reply from 105.224.92.1: bytes=32 time=16ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=14ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=14ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=14ms TTL=254
Reply from 105.224.92.1: bytes=32 time=14ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=16ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=17ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=16ms TTL=254
Reply from 105.224.92.1: bytes=32 time=17ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=14ms TTL=254
Reply from 105.224.92.1: bytes=32 time=14ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254

Ping statistics for 105.224.92.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 17ms, Average = 15ms

2014-03-31 15:28:47.50
Click to expand...

Looking Good!
 
Correct me if I'm wrong but this tool won't differentiate between telkom exchange congestion and ISP congestionso would be a bit unfair on the ISP if they get the blame?
 
My results: 4MB uncapped premium with MWEB.

Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

Pinging 41.133.136.1 with 32 bytes of data:
Reply from 41.133.136.1: bytes=32 time=326ms TTL=254
Reply from 41.133.136.1: bytes=32 time=356ms TTL=254
Reply from 41.133.136.1: bytes=32 time=356ms TTL=254
Reply from 41.133.136.1: bytes=32 time=326ms TTL=254
Reply from 41.133.136.1: bytes=32 time=374ms TTL=254
Reply from 41.133.136.1: bytes=32 time=210ms TTL=254
Reply from 41.133.136.1: bytes=32 time=320ms TTL=254
Reply from 41.133.136.1: bytes=32 time=227ms TTL=254
Reply from 41.133.136.1: bytes=32 time=146ms TTL=254
Reply from 41.133.136.1: bytes=32 time=313ms TTL=254
Request timed out.
Request timed out.
Reply from 41.133.136.1: bytes=32 time=445ms TTL=254
Request timed out.
Reply from 41.133.136.1: bytes=32 time=473ms TTL=254
Reply from 41.133.136.1: bytes=32 time=311ms TTL=254
Reply from 41.133.136.1: bytes=32 time=371ms TTL=254
Reply from 41.133.136.1: bytes=32 time=278ms TTL=254
Reply from 41.133.136.1: bytes=32 time=345ms TTL=254
Reply from 41.133.136.1: bytes=32 time=348ms TTL=254
Reply from 41.133.136.1: bytes=32 time=410ms TTL=254
Reply from 41.133.136.1: bytes=32 time=399ms TTL=254
Reply from 41.133.136.1: bytes=32 time=594ms TTL=254
Reply from 41.133.136.1: bytes=32 time=355ms TTL=254
Reply from 41.133.136.1: bytes=32 time=411ms TTL=254
Reply from 41.133.136.1: bytes=32 time=397ms TTL=254
Reply from 41.133.136.1: bytes=32 time=388ms TTL=254
Reply from 41.133.136.1: bytes=32 time=402ms TTL=254
Reply from 41.133.136.1: bytes=32 time=381ms TTL=254
Reply from 41.133.136.1: bytes=32 time=500ms TTL=254

Ping statistics for 41.133.136.1:
Packets: Sent = 30, Received = 27, Lost = 3 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 146ms, Maximum = 594ms, Average = 361ms

2014/03/31 16:35:00.36
 
wingnut771 said:
Correct me if I'm wrong but this tool won't differentiate between telkom exchange congestion and ISP congestionso would be a bit unfair on the ISP if they get the blame?
Click to expand...

Only telkom congestion/line issues will be detected. Therefore we can deduct that if there is no issues with the line, it must be with the isp - and if there is high latency, the problem is most likely with telkom :)
 
Zertop said:
Only telkom congestion/line issues will be detected. Therefore we can deduct that if there is no issues with the line, it must be with the isp - and if there is high latency, the problem is most likely with telkom :)
Click to expand...

but didn't we establish that if the ISP is congested that one can also have a high 2nd hop?

EDIT: Sorry to put a spanner in the works :)
 
Last edited:
wingnut771 said:
but didn't we establish that if the ISP is congested that one can also have a high 2nd hop?

EDIT: Sorry to put a spanner in the works :)
Click to expand...

We did? :D As far as I understand it, an ipc congestion will only appear on hop 3+, cause although hop 2 belongs to the isp - it is still on telkoms network - as it is still hasnt moved over to the isp's network.
 
Last edited:
Zertop said:
We did? :D As far as I understand it, an ipc congestion will only appear on hop 3+, cause hop 2 is still on telkoms network - as it is the last router before going to the ISPs network.
Click to expand...

"We" as in MyBB forums :D

That's what I had in my head too, don't know why I was suddenly suspecting hop 2 :wtf:
 
OW 4MB Titan Uncapped: seemingly no line issues, so assume it's the ISP...

Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

Pinging 196.210.140.1 with 32 bytes of data:
Reply from 196.210.140.1: bytes=32 time=12ms TTL=254
Reply from 196.210.140.1: bytes=32 time=11ms TTL=254
Reply from 196.210.140.1: bytes=32 time=11ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=11ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=11ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=12ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=14ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=39ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=11ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=11ms TTL=254
Reply from 196.210.140.1: bytes=32 time=11ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=11ms TTL=254
Reply from 196.210.140.1: bytes=32 time=45ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=57ms TTL=254

Ping statistics for 196.210.140.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 57ms, Average = 14ms

31/03/2014 18:51:10.04
 
howardb said:
OW 4MB Titan Uncapped: seemingly no line issues, so assume it's the ISP...

Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

Pinging 196.210.140.1 with 32 bytes of data:
Reply from 196.210.140.1: bytes=32 time=12ms TTL=254
Reply from 196.210.140.1: bytes=32 time=11ms TTL=254
Reply from 196.210.140.1: bytes=32 time=11ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=11ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=11ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=12ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=14ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=39ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=11ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=11ms TTL=254
Reply from 196.210.140.1: bytes=32 time=11ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=11ms TTL=254
Reply from 196.210.140.1: bytes=32 time=45ms TTL=254
Reply from 196.210.140.1: bytes=32 time=10ms TTL=254
Reply from 196.210.140.1: bytes=32 time=57ms TTL=254

Ping statistics for 196.210.140.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 57ms, Average = 14ms

31/03/2014 18:51:10.04
Click to expand...

Hi,

There are a few high hops there - which could cause a few issues. I will be integrating maximum times into my next version.

Z
 
@Zertop: Would it add value to add some weight to the packets of the pinger when testing? When I do a test, I ping with 1400 bytes (just under typical MTU size).
 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)
Bad parameter 27.

Tue 04/01/2014 9:59:19.09
 
lcbxx said:
@Zertop: Would it add value to add some weight to the packets of the pinger when testing? When I do a test, I ping with 1400 bytes (just under typical MTU size).
Click to expand...

I will try it out and possibly include in the next version!

Z
 
crawler said:
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)
Bad parameter 27.

Tue 04/01/2014 9:59:19.09
Click to expand...

Hmm? Strange

I havnt updated the version recently so it should work?

Z
 
Your average ping was Average=ms!

= was unexpected at this time.
Click to expand...
:confused: No result? I used zip. Ran batch in Command prompt box.
 
Okay, it seems that the ping didn't work at all for you? Could you do a manual tracert for me please :)

Z
 
Zertop said:
Okay, it seems that the ping didn't work at all for you? Could you do a manual tracert for me please :)

Z
Click to expand...

Tracing route to mybroadband.co.za [197.242.89.170]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms mifi.afrihost.com
2 94 ms 49 ms 49 ms 41.181.230.241
3 279 ms 419 ms 419 ms 41.181.230.242
4 238 ms 269 ms 269 ms 41.181.230.237
5 218 ms 259 ms 269 ms rb-dca-2.za-qux-f.za.mtnbusiness.net [41.181.248
.232]
6 248 ms 288 ms 289 ms rb-dca-2.za--rb-cr-1.mtnns.net [196.44.31.122]
7 268 ms 299 ms 750 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
8 89 ms 119 ms 79 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]

9 * * * Request timed out.
10 320 ms 307 ms 249 ms CORE.GP-CN-HET-MEE-1.TO.GP-MR-VOD-MEE-1.DFA.P2P.
10G.za.africainx.net [41.84.12.151]
11 258 ms 309 ms 239 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
12 238 ms 299 ms 259 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
13 348 ms 259 ms 279 ms row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
14 268 ms 299 ms 329 ms 197.242.89.170

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms mifi.afrihost.com
2 72 ms 79 ms 179 ms 41.181.230.241
3 278 ms 278 ms 349 ms 41.181.230.242
4 238 ms 259 ms 309 ms 41.181.230.237
5 268 ms 499 ms 339 ms rb-dca-2.za-qux-f.za.mtnbusiness.net [41.1
.232]
6 278 ms 379 ms 319 ms rb-cr-2.za--rb-dca-2.za-b.mtnns.net [196.4
5]
7 278 ms 299 ms 309 ms 41.181.139.99
8 70 ms 88 ms 79 ms 72.14.194.74
9 832 ms 278 ms 209 ms 66.249.95.8
10 491 ms 469 ms 490 ms 209.85.244.240
11 449 ms 479 ms 459 ms 72.14.242.166
12 448 ms 479 ms 509 ms 209.85.252.83
13 * * * Request timed out.
14 2689 ms 1027 ms 218 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.


Afrihost mobile data with MiFi over USB. :(
 
Seriously said:
Tracing route to mybroadband.co.za [197.242.89.170]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms mifi.afrihost.com
2 94 ms 49 ms 49 ms 41.181.230.241
3 279 ms 419 ms 419 ms 41.181.230.242
4 238 ms 269 ms 269 ms 41.181.230.237
5 218 ms 259 ms 269 ms rb-dca-2.za-qux-f.za.mtnbusiness.net [41.181.248
.232]
6 248 ms 288 ms 289 ms rb-dca-2.za--rb-cr-1.mtnns.net [196.44.31.122]
7 268 ms 299 ms 750 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
8 89 ms 119 ms 79 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]

9 * * * Request timed out.
10 320 ms 307 ms 249 ms CORE.GP-CN-HET-MEE-1.TO.GP-MR-VOD-MEE-1.DFA.P2P.
10G.za.africainx.net [41.84.12.151]
11 258 ms 309 ms 239 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
12 238 ms 299 ms 259 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
13 348 ms 259 ms 279 ms row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
14 268 ms 299 ms 329 ms 197.242.89.170

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms mifi.afrihost.com
2 72 ms 79 ms 179 ms 41.181.230.241
3 278 ms 278 ms 349 ms 41.181.230.242
4 238 ms 259 ms 309 ms 41.181.230.237
5 268 ms 499 ms 339 ms rb-dca-2.za-qux-f.za.mtnbusiness.net [41.1
.232]
6 278 ms 379 ms 319 ms rb-cr-2.za--rb-dca-2.za-b.mtnns.net [196.4
5]
7 278 ms 299 ms 309 ms 41.181.139.99
8 70 ms 88 ms 79 ms 72.14.194.74
9 832 ms 278 ms 209 ms 66.249.95.8
10 491 ms 469 ms 490 ms 209.85.244.240
11 449 ms 479 ms 459 ms 72.14.242.166
12 448 ms 479 ms 509 ms 209.85.252.83
13 * * * Request timed out.
14 2689 ms 1027 ms 218 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.


Afrihost mobile data with MiFi over USB. :(
Click to expand...

Remember, there are no line issues with a Mifi device... Therefore the second hop is not pingable :(
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X