This test is only pinging your router. Hence the fantastic pings.
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: How do you normally pay for purchases in stores?
"Is it my Line" Report Tool
- Thread starter Zertop
- Start date
This test is only pinging your router. Hence the fantastic pings.
Strange why is it doing that ?
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\System32>tracert [url]www.google.co.za[/url]
Tracing route to [url]www.google.co.za[/url] [66.8.14.26]
over a maximum of 30 hops:
1 <1 ms 1 ms 1 ms 192.168.1.1
2 8 ms 7 ms 8 ms 105-236-3-129-esr-lo.mtnbusiness.co.za [105.236.
3.129]
3 10 ms 9 ms 10 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178
.65]
4 11 ms 11 ms 10 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 11 ms 10 ms 10 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 10 ms 9 ms 10 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 10 ms 9 ms 10 ms cache.google.com [66.8.14.26]
Trace complete.
C:\Windows\System32>Think it's fixed now..
Router IP 192.168.1.1 was in the DHCP...
Zertop's "Is it my Line" Results
Date/Time: Thu Jul 16 23:27:31 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 62ms.
Your maximum ping was 74ms.
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:
Router IP 192.168.1.1 was in the DHCP...
Zertop's "Is it my Line" Results
Date/Time: Thu Jul 16 23:27:31 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 62ms.
Your maximum ping was 74ms.
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 105.236.3.129 with 32 bytes of data:
Reply from 105.236.3.129: bytes=32 time=58ms TTL=254
Reply from 105.236.3.129: bytes=32 time=56ms TTL=254
Reply from 105.236.3.129: bytes=32 time=58ms TTL=254
Reply from 105.236.3.129: bytes=32 time=63ms TTL=254
Reply from 105.236.3.129: bytes=32 time=62ms TTL=254
Reply from 105.236.3.129: bytes=32 time=61ms TTL=254
Reply from 105.236.3.129: bytes=32 time=60ms TTL=254
Reply from 105.236.3.129: bytes=32 time=63ms TTL=254
Reply from 105.236.3.129: bytes=32 time=65ms TTL=254
Reply from 105.236.3.129: bytes=32 time=63ms TTL=254
Reply from 105.236.3.129: bytes=32 time=64ms TTL=254
Reply from 105.236.3.129: bytes=32 time=60ms TTL=254
Reply from 105.236.3.129: bytes=32 time=62ms TTL=254
Reply from 105.236.3.129: bytes=32 time=59ms TTL=254
Reply from 105.236.3.129: bytes=32 time=71ms TTL=254
Reply from 105.236.3.129: bytes=32 time=74ms TTL=254
Reply from 105.236.3.129: bytes=32 time=64ms TTL=254
Reply from 105.236.3.129: bytes=32 time=64ms TTL=254
Reply from 105.236.3.129: bytes=32 time=61ms TTL=254
Reply from 105.236.3.129: bytes=32 time=71ms TTL=254
Reply from 105.236.3.129: bytes=32 time=60ms TTL=254
Reply from 105.236.3.129: bytes=32 time=60ms TTL=254
Reply from 105.236.3.129: bytes=32 time=60ms TTL=254
Reply from 105.236.3.129: bytes=32 time=63ms TTL=254
Reply from 105.236.3.129: bytes=32 time=63ms TTL=254
Reply from 105.236.3.129: bytes=32 time=58ms TTL=254
Reply from 105.236.3.129: bytes=32 time=62ms TTL=254
Reply from 105.236.3.129: bytes=32 time=57ms TTL=254
Reply from 105.236.3.129: bytes=32 time=63ms TTL=254
Reply from 105.236.3.129: bytes=32 time=64ms TTL=254
Ping statistics for 105.236.3.129:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 74ms, Average = 62msTelkom 4 Mbps ADSL - Afrigreen Capped 4 Mbps DSL
Zertop's "Is it my Line" Results
Date/Time: Thu Jul 16 23:56:49 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 18ms.
Your maximum ping was 101ms.
Looking at your average ping, your line seems to be running perfectly.
Looking at your maximum ping, however, it seems as though there could be a serious intermittent fault on the line. This could be a cause of an issue. Please post the results (at the end of the program) into the forum for advice.
Detailed Report:
Zertop's "Is it my Line" Results
Date/Time: Thu Jul 16 23:56:49 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 18ms.
Your maximum ping was 101ms.
Looking at your average ping, your line seems to be running perfectly.
Looking at your maximum ping, however, it seems as though there could be a serious intermittent fault on the line. This could be a cause of an issue. Please post the results (at the end of the program) into the forum for advice.
Detailed Report:
Code:
Pinging 169.0.14.1 with 32 bytes of data:
Reply from 169.0.14.1: bytes=32 time=11ms TTL=254
Reply from 169.0.14.1: bytes=32 time=10ms TTL=254
Reply from 169.0.14.1: bytes=32 time=11ms TTL=254
Reply from 169.0.14.1: bytes=32 time=11ms TTL=254
Reply from 169.0.14.1: bytes=32 time=10ms TTL=254
Reply from 169.0.14.1: bytes=32 time=18ms TTL=254
Reply from 169.0.14.1: bytes=32 time=10ms TTL=254
Reply from 169.0.14.1: bytes=32 time=10ms TTL=254
Reply from 169.0.14.1: bytes=32 time=10ms TTL=254
Reply from 169.0.14.1: bytes=32 time=10ms TTL=254
Reply from 169.0.14.1: bytes=32 time=10ms TTL=254
Reply from 169.0.14.1: bytes=32 time=11ms TTL=254
Reply from 169.0.14.1: bytes=32 time=33ms TTL=254
Reply from 169.0.14.1: bytes=32 time=10ms TTL=254
Reply from 169.0.14.1: bytes=32 time=63ms TTL=254
Reply from 169.0.14.1: bytes=32 time=24ms TTL=254
Reply from 169.0.14.1: bytes=32 time=10ms TTL=254
Reply from 169.0.14.1: bytes=32 time=11ms TTL=254
Reply from 169.0.14.1: bytes=32 time=10ms TTL=254
Reply from 169.0.14.1: bytes=32 time=44ms TTL=254
Reply from 169.0.14.1: bytes=32 time=101ms TTL=254
Reply from 169.0.14.1: bytes=32 time=12ms TTL=254
Reply from 169.0.14.1: bytes=32 time=11ms TTL=254
Reply from 169.0.14.1: bytes=32 time=11ms TTL=254
Reply from 169.0.14.1: bytes=32 time=11ms TTL=254
Reply from 169.0.14.1: bytes=32 time=11ms TTL=254
Reply from 169.0.14.1: bytes=32 time=11ms TTL=254
Reply from 169.0.14.1: bytes=32 time=10ms TTL=254
Reply from 169.0.14.1: bytes=32 time=15ms TTL=254
Reply from 169.0.14.1: bytes=32 time=39ms TTL=254
Ping statistics for 169.0.14.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 101ms, Average = 18msI'm on a 2MB line, did the test with both my Afrihost and Telkom accounts.
Afrihost:
Zertop's "Is it my Line" Results
Date/Time: Fri Jul 17 15:51:34 CAT 2015
Basic Report:
Your packet loss was 16%.
Your average ping was 428ms.
Your maximum ping was 568ms.
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:
Telkom:
Zertop's "Is it my Line" Results
Date/Time: Fri Jul 17 15:55:00 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 373ms.
Your maximum ping was 567ms.
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:
This stupidly high ping always starts on the 2nd jump in trace routes. Can anyone help?
Afrihost:
Zertop's "Is it my Line" Results
Date/Time: Fri Jul 17 15:51:34 CAT 2015
Basic Report:
Your packet loss was 16%.
Your average ping was 428ms.
Your maximum ping was 568ms.
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 105.236.8.65 with 32 bytes of data:
Request timed out.
Reply from 105.236.8.65: bytes=32 time=469ms TTL=254
Reply from 105.236.8.65: bytes=32 time=459ms TTL=254
Reply from 105.236.8.65: bytes=32 time=483ms TTL=254
Reply from 105.236.8.65: bytes=32 time=422ms TTL=254
Reply from 105.236.8.65: bytes=32 time=381ms TTL=254
Reply from 105.236.8.65: bytes=32 time=398ms TTL=254
Reply from 105.236.8.65: bytes=32 time=335ms TTL=254
Reply from 105.236.8.65: bytes=32 time=380ms TTL=254
Reply from 105.236.8.65: bytes=32 time=439ms TTL=254
Reply from 105.236.8.65: bytes=32 time=504ms TTL=254
Reply from 105.236.8.65: bytes=32 time=528ms TTL=254
Reply from 105.236.8.65: bytes=32 time=568ms TTL=254
Request timed out.
Reply from 105.236.8.65: bytes=32 time=460ms TTL=254
Reply from 105.236.8.65: bytes=32 time=416ms TTL=254
Reply from 105.236.8.65: bytes=32 time=414ms TTL=254
Reply from 105.236.8.65: bytes=32 time=415ms TTL=254
Request timed out.
Request timed out.
Reply from 105.236.8.65: bytes=32 time=484ms TTL=254
Reply from 105.236.8.65: bytes=32 time=504ms TTL=254
Reply from 105.236.8.65: bytes=32 time=441ms TTL=254
Reply from 105.236.8.65: bytes=32 time=405ms TTL=254
Request timed out.
Reply from 105.236.8.65: bytes=32 time=319ms TTL=254
Reply from 105.236.8.65: bytes=32 time=293ms TTL=254
Reply from 105.236.8.65: bytes=32 time=429ms TTL=254
Reply from 105.236.8.65: bytes=32 time=392ms TTL=254
Reply from 105.236.8.65: bytes=32 time=366ms TTL=254
Ping statistics for 105.236.8.65:
Packets: Sent = 30, Received = 25, Lost = 5 (16% loss),
Approximate round trip times in milli-seconds:
Minimum = 293ms, Maximum = 568ms, Average = 428msTelkom:
Zertop's "Is it my Line" Results
Date/Time: Fri Jul 17 15:55:00 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 373ms.
Your maximum ping was 567ms.
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 105.224.136.1 with 32 bytes of data:
Reply from 105.224.136.1: bytes=32 time=498ms TTL=254
Reply from 105.224.136.1: bytes=32 time=528ms TTL=254
Reply from 105.224.136.1: bytes=32 time=567ms TTL=254
Reply from 105.224.136.1: bytes=32 time=440ms TTL=254
Reply from 105.224.136.1: bytes=32 time=325ms TTL=254
Reply from 105.224.136.1: bytes=32 time=325ms TTL=254
Reply from 105.224.136.1: bytes=32 time=307ms TTL=254
Reply from 105.224.136.1: bytes=32 time=301ms TTL=254
Reply from 105.224.136.1: bytes=32 time=284ms TTL=254
Reply from 105.224.136.1: bytes=32 time=315ms TTL=254
Reply from 105.224.136.1: bytes=32 time=312ms TTL=254
Reply from 105.224.136.1: bytes=32 time=417ms TTL=254
Reply from 105.224.136.1: bytes=32 time=399ms TTL=254
Reply from 105.224.136.1: bytes=32 time=323ms TTL=254
Reply from 105.224.136.1: bytes=32 time=243ms TTL=254
Reply from 105.224.136.1: bytes=32 time=212ms TTL=254
Reply from 105.224.136.1: bytes=32 time=295ms TTL=254
Reply from 105.224.136.1: bytes=32 time=329ms TTL=254
Reply from 105.224.136.1: bytes=32 time=291ms TTL=254
Reply from 105.224.136.1: bytes=32 time=325ms TTL=254
Reply from 105.224.136.1: bytes=32 time=354ms TTL=254
Reply from 105.224.136.1: bytes=32 time=393ms TTL=254
Reply from 105.224.136.1: bytes=32 time=396ms TTL=254
Reply from 105.224.136.1: bytes=32 time=472ms TTL=254
Reply from 105.224.136.1: bytes=32 time=485ms TTL=254
Reply from 105.224.136.1: bytes=32 time=511ms TTL=254
Reply from 105.224.136.1: bytes=32 time=403ms TTL=254
Reply from 105.224.136.1: bytes=32 time=372ms TTL=254
Reply from 105.224.136.1: bytes=32 time=383ms TTL=254
Reply from 105.224.136.1: bytes=32 time=410ms TTL=254
Ping statistics for 105.224.136.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 212ms, Maximum = 567ms, Average = 373msThis stupidly high ping always starts on the 2nd jump in trace routes. Can anyone help?
I'm on a 2MB line, did the test with both my Afrihost and Telkom accounts.
Afrihost:
Zertop's "Is it my Line" Results
Date/Time: Fri Jul 17 15:51:34 CAT 2015
Basic Report:
Your packet loss was 16%.
Your average ping was 428ms.
Your maximum ping was 568ms.
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 105.236.8.65 with 32 bytes of data: Request timed out. Reply from 105.236.8.65: bytes=32 time=469ms TTL=254 Reply from 105.236.8.65: bytes=32 time=459ms TTL=254 Reply from 105.236.8.65: bytes=32 time=483ms TTL=254 Reply from 105.236.8.65: bytes=32 time=422ms TTL=254 Reply from 105.236.8.65: bytes=32 time=381ms TTL=254 Reply from 105.236.8.65: bytes=32 time=398ms TTL=254 Reply from 105.236.8.65: bytes=32 time=335ms TTL=254 Reply from 105.236.8.65: bytes=32 time=380ms TTL=254 Reply from 105.236.8.65: bytes=32 time=439ms TTL=254 Reply from 105.236.8.65: bytes=32 time=504ms TTL=254 Reply from 105.236.8.65: bytes=32 time=528ms TTL=254 Reply from 105.236.8.65: bytes=32 time=568ms TTL=254 Request timed out. Reply from 105.236.8.65: bytes=32 time=460ms TTL=254 Reply from 105.236.8.65: bytes=32 time=416ms TTL=254 Reply from 105.236.8.65: bytes=32 time=414ms TTL=254 Reply from 105.236.8.65: bytes=32 time=415ms TTL=254 Request timed out. Request timed out. Reply from 105.236.8.65: bytes=32 time=484ms TTL=254 Reply from 105.236.8.65: bytes=32 time=504ms TTL=254 Reply from 105.236.8.65: bytes=32 time=441ms TTL=254 Reply from 105.236.8.65: bytes=32 time=405ms TTL=254 Request timed out. Reply from 105.236.8.65: bytes=32 time=319ms TTL=254 Reply from 105.236.8.65: bytes=32 time=293ms TTL=254 Reply from 105.236.8.65: bytes=32 time=429ms TTL=254 Reply from 105.236.8.65: bytes=32 time=392ms TTL=254 Reply from 105.236.8.65: bytes=32 time=366ms TTL=254 Ping statistics for 105.236.8.65: Packets: Sent = 30, Received = 25, Lost = 5 (16% loss), Approximate round trip times in milli-seconds: Minimum = 293ms, Maximum = 568ms, Average = 428ms
Telkom:
Zertop's "Is it my Line" Results
Date/Time: Fri Jul 17 15:55:00 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 373ms.
Your maximum ping was 567ms.
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 105.224.136.1 with 32 bytes of data: Reply from 105.224.136.1: bytes=32 time=498ms TTL=254 Reply from 105.224.136.1: bytes=32 time=528ms TTL=254 Reply from 105.224.136.1: bytes=32 time=567ms TTL=254 Reply from 105.224.136.1: bytes=32 time=440ms TTL=254 Reply from 105.224.136.1: bytes=32 time=325ms TTL=254 Reply from 105.224.136.1: bytes=32 time=325ms TTL=254 Reply from 105.224.136.1: bytes=32 time=307ms TTL=254 Reply from 105.224.136.1: bytes=32 time=301ms TTL=254 Reply from 105.224.136.1: bytes=32 time=284ms TTL=254 Reply from 105.224.136.1: bytes=32 time=315ms TTL=254 Reply from 105.224.136.1: bytes=32 time=312ms TTL=254 Reply from 105.224.136.1: bytes=32 time=417ms TTL=254 Reply from 105.224.136.1: bytes=32 time=399ms TTL=254 Reply from 105.224.136.1: bytes=32 time=323ms TTL=254 Reply from 105.224.136.1: bytes=32 time=243ms TTL=254 Reply from 105.224.136.1: bytes=32 time=212ms TTL=254 Reply from 105.224.136.1: bytes=32 time=295ms TTL=254 Reply from 105.224.136.1: bytes=32 time=329ms TTL=254 Reply from 105.224.136.1: bytes=32 time=291ms TTL=254 Reply from 105.224.136.1: bytes=32 time=325ms TTL=254 Reply from 105.224.136.1: bytes=32 time=354ms TTL=254 Reply from 105.224.136.1: bytes=32 time=393ms TTL=254 Reply from 105.224.136.1: bytes=32 time=396ms TTL=254 Reply from 105.224.136.1: bytes=32 time=472ms TTL=254 Reply from 105.224.136.1: bytes=32 time=485ms TTL=254 Reply from 105.224.136.1: bytes=32 time=511ms TTL=254 Reply from 105.224.136.1: bytes=32 time=403ms TTL=254 Reply from 105.224.136.1: bytes=32 time=372ms TTL=254 Reply from 105.224.136.1: bytes=32 time=383ms TTL=254 Reply from 105.224.136.1: bytes=32 time=410ms TTL=254 Ping statistics for 105.224.136.1: Packets: Sent = 30, Received = 30, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 212ms, Maximum = 567ms, Average = 373ms
This stupidly high ping always starts on the 2nd jump in trace routes. Can anyone help?
Definitely, without question, an issue with your line. Have you tried getting Telkom to reset your port?
Z
Yep. No change. Their Twitter account told me to try using the line without the POTS filter and that didn't help. They say "we do not see any congestion on the uplink. Usage is at 30%" so apparently it's not exchange congestion? Logged a fault on the website as well and their reply was "Please note that we have tested your line and also recreated the line por" which I don't really understand but the issue's still not fixed.
Getting kinda fed up with them. I've been having this issue since as far back as April, although it stops happening for maybe a week sometimes before returning. I mean, look at this trace route I just did.
I've been sending them tests with results like this frequently and it just feels like their response is "idunnolol ¯\_(ツ)_/¯". Sucks.
Zertop's "Is it my Line" Results
Date/Time: Fri Jul 17 20:44:52 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 15ms.
Your maximum ping was 179ms.
Looking at your average ping, your line seems to be running perfectly.
Looking at your maximum ping, however, it seems as though there could be a serious intermittent fault on the line. This could be a cause of an issue. Please post the results (at the end of the program) into the forum for advice.
Detailed Report:
Date/Time: Fri Jul 17 20:44:52 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 15ms.
Your maximum ping was 179ms.
Looking at your average ping, your line seems to be running perfectly.
Looking at your maximum ping, however, it seems as though there could be a serious intermittent fault on the line. This could be a cause of an issue. 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=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=179ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms 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 = 9ms, Maximum = 179ms, Average = 15msThat's the worst! The best option is actually to go into your local store, taking these results with. Ask them to move you to a completely different physical port, if possible
Z
Thanks
SirPremacy
Active Member
- Joined
- Aug 15, 2010
- Messages
- 40
- Reaction score
- 1
Hi, need some help please. my internet is very slow when browsing. Did this traceroute now, is it my exchange?
C:\Users\>tracert -d telkom.co.za
Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 92 ms 196 ms 203 ms 105.226.0.5
4 11 ms 10 ms 10 ms 105.226.0.6
5 11 ms 10 ms 10 ms 105.226.0.13
6 10 ms 10 ms 10 ms 165.165.221.153
7 33 ms 33 ms 33 ms 196.43.39.166
8 35 ms 35 ms 35 ms 196.43.23.6
9 37 ms 50 ms 39 ms 196.43.23.30
10 34 ms 34 ms 35 ms 196.43.22.222
Trace complete.
C:\Users\>tracert -d telkom.co.za
Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 92 ms 196 ms 203 ms 105.226.0.5
4 11 ms 10 ms 10 ms 105.226.0.6
5 11 ms 10 ms 10 ms 105.226.0.13
6 10 ms 10 ms 10 ms 165.165.221.153
7 33 ms 33 ms 33 ms 196.43.39.166
8 35 ms 35 ms 35 ms 196.43.23.6
9 37 ms 50 ms 39 ms 196.43.23.30
10 34 ms 34 ms 35 ms 196.43.22.222
Trace complete.
With Openweb it makes no difference. I sent them the evidence but either they can't understand it or they realise it is incriminating
(what I mean is the link to the dslam/man is quick and so the delay is on Openweb's network)
(what I mean is the link to the dslam/man is quick and so the delay is on Openweb's network)
Jakkels1991
Expert Member
Hey Zertop
I need your expert advice once again please:
Zertop's "Is it my Line" Results
Date/Time: Tue Aug 25 18:25:51 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 45ms.
Your maximum ping was 48ms.
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:
I need your expert advice once again please:
Zertop's "Is it my Line" Results
Date/Time: Tue Aug 25 18:25:51 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 45ms.
Your maximum ping was 48ms.
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 105.224.204.1 with 32 bytes of data:
Reply from 105.224.204.1: bytes=32 time=47ms TTL=254
Reply from 105.224.204.1: bytes=32 time=48ms TTL=254
Reply from 105.224.204.1: bytes=32 time=45ms TTL=254
Reply from 105.224.204.1: bytes=32 time=46ms TTL=254
Reply from 105.224.204.1: bytes=32 time=47ms TTL=254
Reply from 105.224.204.1: bytes=32 time=46ms TTL=254
Reply from 105.224.204.1: bytes=32 time=47ms TTL=254
Reply from 105.224.204.1: bytes=32 time=46ms TTL=254
Reply from 105.224.204.1: bytes=32 time=46ms TTL=254
Reply from 105.224.204.1: bytes=32 time=44ms TTL=254
Reply from 105.224.204.1: bytes=32 time=47ms TTL=254
Reply from 105.224.204.1: bytes=32 time=46ms TTL=254
Reply from 105.224.204.1: bytes=32 time=46ms TTL=254
Reply from 105.224.204.1: bytes=32 time=46ms TTL=254
Reply from 105.224.204.1: bytes=32 time=46ms TTL=254
Reply from 105.224.204.1: bytes=32 time=46ms TTL=254
Reply from 105.224.204.1: bytes=32 time=45ms TTL=254
Reply from 105.224.204.1: bytes=32 time=45ms TTL=254
Reply from 105.224.204.1: bytes=32 time=46ms TTL=254
Reply from 105.224.204.1: bytes=32 time=45ms TTL=254
Reply from 105.224.204.1: bytes=32 time=46ms TTL=254
Reply from 105.224.204.1: bytes=32 time=46ms TTL=254
Reply from 105.224.204.1: bytes=32 time=46ms TTL=254
Reply from 105.224.204.1: bytes=32 time=46ms TTL=254
Reply from 105.224.204.1: bytes=32 time=46ms TTL=254
Reply from 105.224.204.1: bytes=32 time=46ms TTL=254
Reply from 105.224.204.1: bytes=32 time=45ms TTL=254
Reply from 105.224.204.1: bytes=32 time=47ms TTL=254
Reply from 105.224.204.1: bytes=32 time=46ms TTL=254
Reply from 105.224.204.1: bytes=32 time=45ms TTL=254
Ping statistics for 105.224.204.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 48ms, Average = 45msHeyo,
The ping's a bit high, yet consistent. Certainly not dodgy enough to cause massive slowdowns. What exactly are you experiencing issues with?
Z
Jakkels1991
Expert Member
Heyo,
The ping's a bit high, yet consistent. Certainly not dodgy enough to cause massive slowdowns. What exactly are you experiencing issues with?
Z
Hey Z
Thanks for the quick response.
I was having stupidly slow speeds. Less than 1mbps on a 4meg line. But I have got some feedback from the Telkom rep who said he managed to get it all cleared up now. Will check when I get home this afternoon and post again.
This is some serious BS
Zertop's "Is it my Line" Results
Date/Time: Sun Aug 30 17:21:10 WAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 1630ms.
Your maximum ping was 2575ms.
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:
Anyone in brackenfell area with issues?
Zertop's "Is it my Line" Results
Date/Time: Sun Aug 30 17:21:10 WAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 1630ms.
Your maximum ping was 2575ms.
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=2095ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2142ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2231ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2164ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2263ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2242ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2493ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2171ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2096ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2135ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2307ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2177ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2269ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2575ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2314ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2083ms TTL=63
Reply from 155.239.255.250: bytes=32 time=321ms TTL=63
Reply from 155.239.255.250: bytes=32 time=448ms TTL=63
Reply from 155.239.255.250: bytes=32 time=260ms TTL=63
Reply from 155.239.255.250: bytes=32 time=206ms TTL=63
Reply from 155.239.255.250: bytes=32 time=480ms TTL=63
Reply from 155.239.255.250: bytes=32 time=70ms TTL=63
Reply from 155.239.255.250: bytes=32 time=205ms TTL=63
Reply from 155.239.255.250: bytes=32 time=325ms TTL=63
Reply from 155.239.255.250: bytes=32 time=784ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1600ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2188ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2183ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1914ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2170ms 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 = 70ms, Maximum = 2575ms, Average = 1630msAnyone in brackenfell area with issues?