High ping

S

SurfingPanda

Member
Joined
Jun 6, 2016
Messages
10
Reaction score
0
Ping surges on both Axxess and Telkom account on multiple computers.

Ping is normal during the AM until about 12PM.
Around 12PM - 3PM it goes normal/abnormal erratically.
4PM and later its 300ms+ consistently

Code: 
traceroute to [url]www.google.co.za[/url] (216.58.223.3), 30 hops max, 60 byte packets
 1  login.router (10.0.0.2)  0.658 ms  0.933 ms  1.530 ms
 2  41.170.69.65 (41.170.69.65)  327.673 ms  330.366 ms  333.025 ms
 3  * * *
 4  cpt (169.1.5.94)  346.034 ms  347.371 ms  350.082 ms
 5  cpt (169.1.5.128)  352.520 ms  354.788 ms  358.665 ms
 6  41.164.52.40 (41.164.52.40)  360.870 ms  353.954 ms  355.950 ms
 7  172.18.1.162 (172.18.1.162)  375.659 ms  288.255 ms  264.155 ms
 8  72.14.194.206 (72.14.194.206)  267.795 ms  271.986 ms  272.332 ms
 9  72.14.237.239 (72.14.237.239)  274.910 ms  276.727 ms  279.478 ms
10  jnb01s07-in-f3.1e100.net (216.58.223.3)  282.159 ms  286.033 ms  286.503 ms

Can anyone help? Not sure whats going on...
 
Thx for reply

Results using different filter

Code: 
traceroute to [url]www.google.co.za[/url] (216.58.223.3), 30 hops max, 60 byte packets
 1  login.router (10.0.0.2)  0.758 ms  1.062 ms  1.387 ms
 2  41.170.69.65 (41.170.69.65)  352.255 ms  356.180 ms  359.312 ms
 3  * * *
 4  cpt-rx1.ip.adsl.co.za (169.1.5.94)  375.594 ms  377.668 ms  380.070 ms
 5  cpt-net1.ip.adsl.co.za (169.1.5.128)  383.673 ms  387.202 ms  391.386 ms
 6  41.164.52.40 (41.164.52.40)  394.187 ms  387.669 ms  389.532 ms
 7  172.18.1.162 (172.18.1.162)  415.217 ms  366.080 ms  363.302 ms
 8  72.14.194.206 (72.14.194.206)  366.180 ms  368.690 ms  371.177 ms
 9  72.14.237.239 (72.14.237.239)  373.342 ms  376.389 ms  378.363 ms
10  [url]www.google.co.za[/url] (216.58.223.3)  380.607 ms  383.265 ms  385.491 ms
 
SurfingPanda said:
Ping surges on both Axxess and Telkom account on multiple computers.

Ping is normal during the AM until about 12PM.
Around 12PM - 3PM it goes normal/abnormal erratically.
4PM and later its 300ms+ consistently

Can anyone help? Not sure whats going on...
Click to expand...

I don't know much about this, but logically, if the same things are happening every day around the same times, on 2 different ISP's then I'd think it's exchange congestion. I hardly think changing the filter would do anything, as a result.

Send private messages to TelkomZA & The Axxess Lady on this forum / Twitter / Facebook, with your details (phone no. etc.), and ask them to look into it for you - at the very least, confirm it's the exchange that's the issue.
 
It may not be exchange congestion.

I find myself 600m from exchange as the cable runs and 400m as the road runs. Still, I suffer from 30-60ms pings due to Telkom's enforced interleaved policy over my line. It really screws with everything so much so that attenuation and noise margins differ insanely from time-to-time.
 
SurfingPanda said:
Ping surges on both Axxess and Telkom account on multiple computers.

Ping is normal during the AM until about 12PM.
Around 12PM - 3PM it goes normal/abnormal erratically.
4PM and later its 300ms+ consistently

Code: 
traceroute to [url]www.google.co.za[/url] (216.58.223.3), 30 hops max, 60 byte packets
 1  login.router (10.0.0.2)  0.658 ms  0.933 ms  1.530 ms
 2  41.170.69.65 (41.170.69.65)  327.673 ms  330.366 ms  333.025 ms
 3  * * *
 4  cpt (169.1.5.94)  346.034 ms  347.371 ms  350.082 ms
 5  cpt (169.1.5.128)  352.520 ms  354.788 ms  358.665 ms
 6  41.164.52.40 (41.164.52.40)  360.870 ms  353.954 ms  355.950 ms
 7  172.18.1.162 (172.18.1.162)  375.659 ms  288.255 ms  264.155 ms
 8  72.14.194.206 (72.14.194.206)  267.795 ms  271.986 ms  272.332 ms
 9  72.14.237.239 (72.14.237.239)  274.910 ms  276.727 ms  279.478 ms
10  jnb01s07-in-f3.1e100.net (216.58.223.3)  282.159 ms  286.033 ms  286.503 ms

Can anyone help? Not sure whats going on...
Click to expand...

Looks like you're using us for your DSL.
Strange seeing that it looks like your router is announcing the gateway as a hop, shouldn't be doing that.

What DNS servers are you using?
 
Thanks for reply.

DNS setting currently set to "User configured then Auto Discovered"

traceroute to bras.afrihost.com (155.239.255.250), 30 hops max, 60 byte packets

Code: 
 1  login.router (10.0.0.2)  1.126 ms  1.391 ms  1.729 ms
 2  41.170.69.65 (41.170.69.65)  352.511 ms  354.396 ms  356.583 ms
 3  * * *
 4  cpt-rx1.ip.adsl.co.za (169.1.5.94)  369.980 ms  371.769 ms  374.894 ms
 5  cpt-net1.ip.adsl.co.za (169.1.5.128)  379.841 ms  381.541 ms  383.970 ms
 6  41.164.52.40 (41.164.52.40)  388.241 ms  380.168 ms  383.803 ms
 7  wblv-ip-se-2-wan.telkom-ipnet.co.za (196.25.3.101)  385.560 ms  338.594 ms  369.831 ms
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
 
SurfingPanda said:
Thanks for reply.

DNS setting currently set to "User configured then Auto Discovered"

traceroute to bras.afrihost.com (155.239.255.250), 30 hops max, 60 byte packets

-snip
Click to expand...

Definitely something strange happening here.
Try switching to auto-assigned DNS or even Google's DNS servers to see if this helps.

Any other special setups running on your end?

Your traceroute should look similar to this, shouldn't be querying the gateway.

Code: 
traceroute to google.co.za (216.58.223.3), 64 hops max, 52 byte packets
 1  192.168.1.2 (192.168.1.2)  0.374 ms  0.164 ms  0.147 ms
 2  * * *
 3  cpt-up1.ip.adsl.co.za (169.1.5.105)  18.208 ms  17.952 ms  18.746 ms
 4  cpt-up2.ip.adsl.co.za (169.1.5.106)  17.685 ms  17.650 ms  16.914 ms
 5  cpt-net1.ip.adsl.co.za (169.1.5.128)  17.881 ms  17.693 ms  17.819 ms
 6  41.164.52.40 (41.164.52.40)  19.367 ms  17.826 ms  17.879 ms
 7  172.18.1.162 (172.18.1.162)  39.390 ms  38.849 ms  38.436 ms
 8  72.14.194.206 (72.14.194.206)  39.362 ms  39.290 ms  41.040 ms
 9  72.14.237.239 (72.14.237.239)  39.783 ms  39.323 ms  39.936 ms
10  jnb01s07-in-f3.1e100.net (216.58.223.3)  39.412 ms  38.387 ms  39.081 ms
 
AfriGuy said:
Definitely something strange happening here.
Try switching to auto-assigned DNS or even Google's DNS servers to see if this helps.

Any other special setups running on your end?

Your traceroute should look similar to this, shouldn't be querying the gateway.

Code: 
traceroute to google.co.za (216.58.223.3), 64 hops max, 52 byte packets
 1  192.168.1.2 (192.168.1.2)  0.374 ms  0.164 ms  0.147 ms
 2  * * *
 3  cpt-up1.ip.adsl.co.za (169.1.5.105)  18.208 ms  17.952 ms  18.746 ms
 4  cpt-up2.ip.adsl.co.za (169.1.5.106)  17.685 ms  17.650 ms  16.914 ms
 5  cpt-net1.ip.adsl.co.za (169.1.5.128)  17.881 ms  17.693 ms  17.819 ms
 6  41.164.52.40 (41.164.52.40)  19.367 ms  17.826 ms  17.879 ms
 7  172.18.1.162 (172.18.1.162)  39.390 ms  38.849 ms  38.436 ms
 8  72.14.194.206 (72.14.194.206)  39.362 ms  39.290 ms  41.040 ms
 9  72.14.237.239 (72.14.237.239)  39.783 ms  39.323 ms  39.936 ms
10  jnb01s07-in-f3.1e100.net (216.58.223.3)  39.412 ms  38.387 ms  39.081 ms
Click to expand...

If it's set up as an access point, it will show up on the traceroute...
Code: 
Tracing route to google.co.za [216.58.223.35]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  ARCHER_D5 [192.168.0.1] <-Access Point
  2    <1 ms    <1 ms    <1 ms  home.gateway.pace.net [192.168.1.1] <-Router
  3     *        *
 
Johnatan56 said:
If it's set up as an access point, it will show up on the traceroute...
Code: 
Tracing route to google.co.za [216.58.223.35]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  ARCHER_D5 [192.168.0.1] <-Access Point
  2    <1 ms    <1 ms    <1 ms  home.gateway.pace.net [192.168.1.1] <-Router
  3     *        *
Click to expand...

Your gateway, yes, not our initial gateway :)
 
With Auto-discovered DNS:

Code: 
traceroute to bras.afrihost.com (155.239.255.250), 30 hops max, 60 byte packets
 1  login.router (10.0.0.2)  0.886 ms  1.356 ms  1.699 ms
 2  41.170.69.65 (41.170.69.65)  265.387 ms  267.064 ms  269.261 ms
 3  * * *
 4  cpt-rx1.ip.adsl.co.za (169.1.5.94)  281.165 ms  282.675 ms  284.620 ms
 5  cpt-net1.ip.adsl.co.za (169.1.5.128)  288.890 ms  290.025 ms  292.669 ms
 6  41.164.52.40 (41.164.52.40)  295.737 ms  289.757 ms  293.821 ms
 7  wblv-ip-se-2-wan.telkom-ipnet.co.za (196.25.3.101)  294.423 ms  245.083 ms  395.394 ms
 8  196.43.25.205 (196.43.25.205)  395.518 ms !H * *


With Google DNS servers 8.8.8.8, 8.8.8.4:

Code: 
traceroute to bras.afrihost.com (155.239.255.250), 30 hops max, 60 byte packets
 1  login.router (10.0.0.2)  0.990 ms  1.251 ms  1.548 ms
 2  41.170.69.65 (41.170.69.65)  227.322 ms  229.724 ms  232.781 ms
 3  cpt-tx2.ip.adsl.co.za (169.1.5.81)  1101.827 ms  1102.582 ms  1199.692 ms
 4  cpt-rx1.ip.adsl.co.za (169.1.5.94)  249.877 ms  250.223 ms  251.851 ms
 5  cpt-net1.ip.adsl.co.za (169.1.5.128)  254.317 ms  256.688 ms  259.077 ms
 6  41.164.52.40 (41.164.52.40)  262.168 ms  256.052 ms  258.425 ms
 7  wblv-ip-se-2-wan.telkom-ipnet.co.za (196.25.3.101)  261.759 ms  188.023 ms  376.470 ms
 8  196.43.25.205 (196.43.25.205)  377.302 ms !H * *
My setup: 1 router with almost factory settings, except for access details to connect, DNS settings from Axxess website & different login password to router. Have 2 micro-filters for phones with WIFI disabled, connecting through ethernet.
 
Last edited:
SurfingPanda said:
With Auto-discovered DNS:

-snip
My setup: 1 router with almost factory settings, except for access details to connect, DNS settings from Axxess website & different login password to router. Have 2 micro-filters for phones with WIFI disabled, connecting through ethernet.
Click to expand...

Hhmm. Do you perhaps have a different router to test with?
 
With Netgear DGN 2200

Code: 
traceroute to bras.afrihost.com (155.239.255.250), 30 hops max, 60 byte packets
 1  10.0.0.2 (10.0.0.2)  0.227 ms  0.260 ms  0.342 ms
 2  41.170.69.65 (41.170.69.65)  343.730 ms  346.824 ms  348.608 ms
 3  cpt-tx2.ip.adsl.co.za (169.1.5.81)  358.262 ms * *
 4  cpt-rx1.ip.adsl.co.za (169.1.5.94)  361.541 ms  361.642 ms  364.481 ms
 5  cpt-net1.ip.adsl.co.za (169.1.5.128)  366.187 ms  367.834 ms  369.480 ms
 6  41.164.52.40 (41.164.52.40)  371.400 ms  356.274 ms  359.461 ms
 7  wblv-ip-se-2-wan.telkom-ipnet.co.za (196.25.3.101)  361.192 ms  244.552 ms  247.796 ms
 8  196.43.25.205 (196.43.25.205)  248.985 ms !H * *

If I do the same test 2-3 hours from now I bet I'll get around 20-30ms. Will post results shortly.


I O U said:
I don't know much about this, but logically, if the same things are happening every day around the same times, on 2 different ISP's then I'd think it's exchange congestion. I hardly think changing the filter would do anything, as a result.

Send private messages to TelkomZA & The Axxess Lady on this forum / Twitter / Facebook, with your details (phone no. etc.), and ask them to look into it for you - at the very least, confirm it's the exchange that's the issue.
Click to expand...

Got message from TelkomZA, was told its exchange related.

Edit: Was too tired to do AM test, fell asleep :o
 
Last edited:
SurfingPanda said:
With Netgear DGN 2200

-snip

If I do the same test 2-3 hours from now I bet I'll get around 20-30ms. Will post results shortly.


Got message from TelkomZA, was told its exchange related.

Edit: Was too tired to do AM test, fell asleep :o
Click to expand...

Could very well be an exchange config related issue - still not sure how/ why you're reaching our gateway here.
What's the experience like testing with another ISP?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X