Terrible pings

C

catman37

Expert Member
Joined
Apr 8, 2012
Messages
1,384
Reaction score
81
Location
East Rand
Hi All,

Please check below tracert. Is this congested exchange or ISP?

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

1 2 ms 2 ms 3 ms 10.0.0.2
2 * * * Request timed out.
3 420 ms 384 ms 430 ms jhb-up3.ip.adsl.co.za [169.1.5.29]
4 530 ms 402 ms 514 ms jhb-in1.ip.adsl.co.za [169.1.5.42]
5 520 ms 427 ms 488 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 490 ms 506 ms 509 ms 169-1-5-243.ip.afrihost.co.za [169.1.5.243]
7 528 ms 505 ms 428 ms 72.14.239.129
8 434 ms 510 ms 512 ms www.google.co.za [216.58.223.35]

or

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

1 3 ms 3 ms 3 ms 10.0.0.2
2 * * * Request timed out.
3 * * 417 ms jhb-up3.ip.adsl.co.za [169.1.5.29]
4 447 ms 402 ms 394 ms jhb-in2.ip.adsl.co.za [169.1.5.30]
5 389 ms 381 ms 520 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 400 ms 390 ms 394 ms 169-1-5-74.ip.afrihost.co.za [169.1.5.74]
7 461 ms 407 ms 411 ms 41.169.57.216
8 421 ms 406 ms 405 ms mtnns-2.jinx.net.za [196.223.14.31]
9 458 ms 458 ms 407 ms jh-cr-1.za-jh-pr-1.za-a.mtnns.net [196.44.0.73]
10 507 ms 509 ms 407 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
11 414 ms 408 ms 405 ms www.afrihost.co.za [41.181.185.18]


Thanks
 
Zertop's LineTool Results
Date/Time: Thu Feb 25 20:52:09 SAST 2016

Basic Report:

Your packet loss was 3%.
Your average ping was 585ms.
Your maximum ping was 904ms.

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: 
PING 155.239.255.250 (155.239.255.250) 56(84) bytes of data.
64 bytes from 155.239.255.250: icmp_seq=1 ttl=63 time=522 ms
64 bytes from 155.239.255.250: icmp_seq=2 ttl=63 time=904 ms
64 bytes from 155.239.255.250: icmp_seq=3 ttl=63 time=514 ms
64 bytes from 155.239.255.250: icmp_seq=4 ttl=63 time=617 ms
64 bytes from 155.239.255.250: icmp_seq=5 ttl=63 time=547 ms
64 bytes from 155.239.255.250: icmp_seq=7 ttl=63 time=535 ms
64 bytes from 155.239.255.250: icmp_seq=8 ttl=63 time=521 ms
64 bytes from 155.239.255.250: icmp_seq=9 ttl=63 time=526 ms
64 bytes from 155.239.255.250: icmp_seq=10 ttl=63 time=542 ms
64 bytes from 155.239.255.250: icmp_seq=11 ttl=63 time=567 ms
64 bytes from 155.239.255.250: icmp_seq=12 ttl=63 time=496 ms
64 bytes from 155.239.255.250: icmp_seq=13 ttl=63 time=512 ms
64 bytes from 155.239.255.250: icmp_seq=14 ttl=63 time=527 ms
64 bytes from 155.239.255.250: icmp_seq=15 ttl=63 time=656 ms
64 bytes from 155.239.255.250: icmp_seq=16 ttl=63 time=574 ms
64 bytes from 155.239.255.250: icmp_seq=17 ttl=63 time=493 ms
64 bytes from 155.239.255.250: icmp_seq=18 ttl=63 time=518 ms
64 bytes from 155.239.255.250: icmp_seq=19 ttl=63 time=637 ms
64 bytes from 155.239.255.250: icmp_seq=20 ttl=63 time=555 ms
64 bytes from 155.239.255.250: icmp_seq=21 ttl=63 time=575 ms
64 bytes from 155.239.255.250: icmp_seq=22 ttl=63 time=702 ms
64 bytes from 155.239.255.250: icmp_seq=23 ttl=63 time=623 ms
64 bytes from 155.239.255.250: icmp_seq=24 ttl=63 time=539 ms
64 bytes from 155.239.255.250: icmp_seq=25 ttl=63 time=560 ms
64 bytes from 155.239.255.250: icmp_seq=26 ttl=63 time=603 ms
64 bytes from 155.239.255.250: icmp_seq=27 ttl=63 time=586 ms
64 bytes from 155.239.255.250: icmp_seq=28 ttl=63 time=583 ms
64 bytes from 155.239.255.250: icmp_seq=29 ttl=63 time=748 ms
64 bytes from 155.239.255.250: icmp_seq=30 ttl=63 time=665 ms

--- 155.239.255.250 ping statistics ---
30 packets transmitted, 29 received, 3% packet loss, time 29082ms
rtt min/avg/max/mdev = 493.586/585.000/904.383/86.083 ms
 
catman37 said:
Zertop's LineTool Results
Date/Time: Thu Feb 25 20:52:09 SAST 2016

Basic Report:

Your packet loss was 3%.
Your average ping was 585ms.
Your maximum ping was 904ms.

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: 
PING 155.239.255.250 (155.239.255.250) 56(84) bytes of data.
64 bytes from 155.239.255.250: icmp_seq=1 ttl=63 time=522 ms
64 bytes from 155.239.255.250: icmp_seq=2 ttl=63 time=904 ms
64 bytes from 155.239.255.250: icmp_seq=3 ttl=63 time=514 ms
64 bytes from 155.239.255.250: icmp_seq=4 ttl=63 time=617 ms
64 bytes from 155.239.255.250: icmp_seq=5 ttl=63 time=547 ms
64 bytes from 155.239.255.250: icmp_seq=7 ttl=63 time=535 ms
64 bytes from 155.239.255.250: icmp_seq=8 ttl=63 time=521 ms
64 bytes from 155.239.255.250: icmp_seq=9 ttl=63 time=526 ms
64 bytes from 155.239.255.250: icmp_seq=10 ttl=63 time=542 ms
64 bytes from 155.239.255.250: icmp_seq=11 ttl=63 time=567 ms
64 bytes from 155.239.255.250: icmp_seq=12 ttl=63 time=496 ms
64 bytes from 155.239.255.250: icmp_seq=13 ttl=63 time=512 ms
64 bytes from 155.239.255.250: icmp_seq=14 ttl=63 time=527 ms
64 bytes from 155.239.255.250: icmp_seq=15 ttl=63 time=656 ms
64 bytes from 155.239.255.250: icmp_seq=16 ttl=63 time=574 ms
64 bytes from 155.239.255.250: icmp_seq=17 ttl=63 time=493 ms
64 bytes from 155.239.255.250: icmp_seq=18 ttl=63 time=518 ms
64 bytes from 155.239.255.250: icmp_seq=19 ttl=63 time=637 ms
64 bytes from 155.239.255.250: icmp_seq=20 ttl=63 time=555 ms
64 bytes from 155.239.255.250: icmp_seq=21 ttl=63 time=575 ms
64 bytes from 155.239.255.250: icmp_seq=22 ttl=63 time=702 ms
64 bytes from 155.239.255.250: icmp_seq=23 ttl=63 time=623 ms
64 bytes from 155.239.255.250: icmp_seq=24 ttl=63 time=539 ms
64 bytes from 155.239.255.250: icmp_seq=25 ttl=63 time=560 ms
64 bytes from 155.239.255.250: icmp_seq=26 ttl=63 time=603 ms
64 bytes from 155.239.255.250: icmp_seq=27 ttl=63 time=586 ms
64 bytes from 155.239.255.250: icmp_seq=28 ttl=63 time=583 ms
64 bytes from 155.239.255.250: icmp_seq=29 ttl=63 time=748 ms
64 bytes from 155.239.255.250: icmp_seq=30 ttl=63 time=665 ms

--- 155.239.255.250 ping statistics ---
30 packets transmitted, 29 received, 3% packet loss, time 29082ms
rtt min/avg/max/mdev = 493.586/585.000/904.383/86.083 ms
Click to expand...

That ping is to the exchange, hinting at the issue being between the exchange and you. Try turning off the WiFi and running the test with only the desktop running via ethernet.
 
Hi Afriguy

I tried a friends modem and telkom account.

I received this message from Telkom on the 13th...since then I have had this issue.

Dear customer, please note that Telkom has identified a network outage in your area. If your service is affected, you may report a fault by replying Yes to this message within 24 hours. If you are unable to reply within the first 24 hours, please call 10210 (Residential) or 10217 (Business). Telkom


Thanks
 
Last edited:
catman37 said:
Hi Afriguy

I tried a friends modem and telkom account.

I received this message from Telkom on the 13th...since then I have had this issue.

Dear customer, please note that Telkom has identified a network outage in your area. If your service is affected, you may report a fault by replying Yes to this message within 24 hours. If you are unable to reply within the first 24 hours, please call 10210 (Residential) or 10217 (Business). Telkom


Thanks
Click to expand...
I received a similar message a few days ago and since then my pings are very bad. Mostly from about 16:00 onwards.

I logged a fault with Telkom but nothing yet.
 
Yes I am.

I have left it thinking it would get better but it isn't.

Here is a speed test from 17h30. What I don't understand is why the download has shot up to 9.8mb. I normally only get 8.2mb.



.
442aefcc2c42827537169668a8444950.jpg
 
Last edited:
Yip me too. They better fixed it soon.

You should log a fault as well.

uploadfromtaptalk1456503076278.jpg
 
Last edited:
Just spoke to a Telkom tech in the street. He says on the 13th they upgraded all the equipment to MSAM 3. Which he says is the latest.

He said he would let the exchange manager now.
 
catman37 said:
Just spoke to a Telkom tech in the street. He says on the 13th they upgraded all the equipment to MSAM 3. Which he says is the latest.

He said he would let the exchange manager now.
Click to expand...
Thanks for the update, hopefully they can sort it out.
 
Received a message from telkom this morning to say my fault is closed and all services are restored. I highly doubt it but will test later.

I tested it just now and my ping was 24ms but the problem normally starts late afternoon only.
 
Last edited:
Received this from Telkomza

Morning

The line seems OK, traffic on the Bardene MSAN you connecting to also seems OK, I however investigated another complaint from a client on Bardene 5 and traffic substantially lower than usual so suspect we might be looking at something in the area.
Have already requested a NF for investigation and mailed one of the senior engineers to have a look as well.

Would appreciate if you can send me a trace to www.myadsl.co.za , should assist me to investigate further, unfortunately unable to get hold of a SAIX test account presently so your own account will have to suffice.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X