- Joined
- Oct 9, 2014
- Messages
- 7,265
- Reaction score
- 6
Sorry only seeing this now, it was the entire site.
I tried rebooting the router but the issue persisted.
How are your speeds looking at the moment? Is Youtube watchable?
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Sorry only seeing this now, it was the entire site.
I tried rebooting the router but the issue persisted.
Davedes, it's all good, thanks for the support. Right now, it's 20:45, I'm speedtesting ookla through my nearest Telkom exchange, ping at 12ms and download at 9.75 mbps! Thats to Webafrica, no more drama..
AfriGenie, you're scripting to the best of your ability, but there's a BIG problem somewhere, the sooner you\Critical Care realize and admit to it, the quicker the noise will go away. (PS: I never got ONE reply from them today. Been getting 2 to 3 emails a day, but after I emailed the crappy figures last night, and the fact I've moved to Webafrica, the Critical Care people didn't even have the decency to reply to my email, or to say thank, we appreciate you taking the time out of your evening to try assist us!
I'm over it. Hope you have a good evening nonetheless.
Alan
So if his issue isn't related to shaping then it's capacity issues!
![]()
How are your speeds looking at the moment? Is Youtube watchable?
Based on what I can see it's not IPC that's causing the problem. The latency spike is on a router interface within the Afrihost network, before it breaks out. In addition tracing to an IP address within the Afrihost network shouldn't break out at all i.e. 169.1.1.36 but the latency spike is till there.
cpt-tx2.ip.adsl.co.za (169.1.5.81) - 0 | 32 | 32 | 134 | 158 | 180 | 144 |
So, either (1) that router processor is struggling, (2) the physical interface is oversubscribed at times, (3) shaping/qos/policy is being applied on that interface. My humble opinion.
Based on what I can see it's not IPC that's causing the problem. The latency spike is on a router interface within the Afrihost network, before it breaks out. In addition tracing to an IP address within the Afrihost network shouldn't break out at all i.e. 169.1.1.36 but the latency spike is till there.
cpt-tx2.ip.adsl.co.za (169.1.5.81) - 0 | 32 | 32 | 134 | 158 | 180 | 144 |
So, either (1) that router processor is struggling, (2) the physical interface is oversubscribed at times, (3) shaping/qos/policy is being applied on that interface. My humble opinion.
And this router happens to spike every night at the same time like clockwork?

********************************* Packets************** Pings
*Host************************** Loss%** Snt** Last** Avg* Best* Wrst StDev
*1. router.asus.com************* 0.0%*** 60*** 0.2** 0.3** 0.2** 0.4** 0.0
*2. ???
*3. cpt-up1.ip.adsl.co.za******* 8.3%*** 60** 20.0* 21.3* 19.2* 42.4** 5.2
*4. cpt-up2.ip.adsl.co.za******* 0.0%*** 60** 20.3* 21.1* 19.4* 37.3** 3.0
*5. cpt-net1.ip.adsl.co.za****** 0.0%*** 60** 19.9* 21.4* 19.3* 54.5** 5.4
*6. optinet.ixp.capetown******** 0.0%*** 60** 22.7* 22.0* 19.8* 53.9** 4.5
*7. bu-ether1.cpt-p-1.optinet.n* 0.0%*** 60** 42.6* 43.7* 41.0* 58.2** 2.9
*8. te0-0-0-0.vic-p-2.optinet.n* 0.0%*** 60** 50.9* 50.9* 47.8* 65.4** 2.6
*9. 197-80-7-15.jhb.mweb.co.za** 0.0%*** 60** 47.6* 48.4* 46.8* 60.7** 2.0
10. bu-ether1.tis-pe-2.optinet.* 0.0%*** 60** 48.0* 49.5* 47.6* 70.3** 4.1
11. bu-ether2.tis-pe-1.optinet.* 0.0%*** 60** 48.1* 49.5* 47.0* 74.8** 5.3
12. 197-80-97-46.jhb.mweb.co.za* 0.0%*** 60** 48.0* 49.0* 47.2* 69.2** 3.5
13. 197-80-247-82.jhb.mweb.co.z* 0.0%*** 60** 40.8* 41.3* 39.8* 57.7** 2.8
14. ???
Hi AfriGenie,
I see that there's been a routing change to the DSTV CDN. Latency looks good. Haven't tested yet as I'm not home currently. There does still appear to be an issue at the IPC hop. Can you please ask the NOC team to comment. Trace below. Thx
Code:********************************* Packets************** Pings *Host************************** Loss%** Snt** Last** Avg* Best* Wrst StDev *1. router.asus.com************* 0.0%*** 60*** 0.2** 0.3** 0.2** 0.4** 0.0 *2. ??? *3. cpt-up1.ip.adsl.co.za******* 8.3%*** 60** 20.0* 21.3* 19.2* 42.4** 5.2 *4. cpt-up2.ip.adsl.co.za******* 0.0%*** 60** 20.3* 21.1* 19.4* 37.3** 3.0 *5. cpt-net1.ip.adsl.co.za****** 0.0%*** 60** 19.9* 21.4* 19.3* 54.5** 5.4 *6. optinet.ixp.capetown******** 0.0%*** 60** 22.7* 22.0* 19.8* 53.9** 4.5 *7. bu-ether1.cpt-p-1.optinet.n* 0.0%*** 60** 42.6* 43.7* 41.0* 58.2** 2.9 *8. te0-0-0-0.vic-p-2.optinet.n* 0.0%*** 60** 50.9* 50.9* 47.8* 65.4** 2.6 *9. 197-80-7-15.jhb.mweb.co.za** 0.0%*** 60** 47.6* 48.4* 46.8* 60.7** 2.0 10. bu-ether1.tis-pe-2.optinet.* 0.0%*** 60** 48.0* 49.5* 47.6* 70.3** 4.1 11. bu-ether2.tis-pe-1.optinet.* 0.0%*** 60** 48.1* 49.5* 47.0* 74.8** 5.3 12. 197-80-97-46.jhb.mweb.co.za* 0.0%*** 60** 48.0* 49.0* 47.2* 69.2** 3.5 13. 197-80-247-82.jhb.mweb.co.z* 0.0%*** 60** 40.8* 41.3* 39.8* 57.7** 2.8 14. ???
HTTP request sent, awaiting response... 200 OK
Length: 10240000000 (9,5G) [application/octet-stream]
Saving to: ‘test.bin’
0% [ ] 13*047*561 390KB/s eta 6h 34m
Afrixxx, If it helps your team, I noticed something else:
A test to SAIX speedtest server in Cape Town from PE:
View attachment 424210
Weirdly a trace to the MWeb based ST server is perfect
View attachment 424204
So I checked the IP's. SAIX is 196.25.37.14, MWEB is 197.84.150.123
Importantly these two routes don't follow the same path in Cape Town.
SAIX:
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 14 | 14 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| cpt-tx2.ip.adsl.co.za - 0 | 14 | 14 | 150 | 168 | 183 | 162 |
| cpt-rx1.ip.adsl.co.za - 0 | 14 | 14 | 26 | 27 | 28 | 27 |
| cpt-net1.ip.adsl.co.za - 10 | 10 | 9 | 26 | 34 | 87 | 27 |
| 41.164.52.40 - 0 | 14 | 14 | 33 | 35 | 55 | 33 |
| wblv-ip-se-2-wan.telkom-ipnet.co.za - 0 | 14 | 14 | 34 | 34 | 35 | 34 |
| 196.43.25.205 - 0 | 14 | 14 | 40 | 43 | 46 | 45 |
| 196.43.39.62 - 0 | 14 | 14 | 157 | 177 | 193 | 173 |
|wblv-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za - 10 | 10 | 9 | 123 | 143 | 169 | 153 |
| wblv-ip-dlr-15-3.saix.net - 0 | 13 | 13 | 150 | 170 | 185 | 156 |
MWEB
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 20 | 20 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| cpt-tx2.ip.adsl.co.za - 0 | 20 | 20 | 106 | 162 | 191 | 179 |
| 169-1-21-54.ip.afrihost.co.za - 0 | 20 | 20 | 132 | 160 | 173 | 148 |
| cpt-net1.ip.adsl.co.za - 6 | 17 | 16 | 26 | 30 | 96 | 26 |
| optinet.ixp.capetown - 0 | 20 | 20 | 34 | 34 | 37 | 37 |
| 201.te0-0-2-2.cpt-pe-13.optinet.net - 0 | 20 | 20 | 35 | 86 | 247 | 91 |
| cpt-ntp.mweb.co.za - 0 | 20 | 20 | 126 | 153 | 167 | 167 |
Hop 4 is different. So although the latency is high on both there is a massive difference in throughput.
Make of that what you will.
Hi AfriGenie,
I see that there's been a routing change to the DSTV CDN. Latency looks good. Haven't tested yet as I'm not home currently. There does still appear to be an issue at the IPC hop. Can you please ask the NOC team to comment. Trace below. Thx
Code:********************************* Packets************** Pings *Host************************** Loss%** Snt** Last** Avg* Best* Wrst StDev *1. router.asus.com************* 0.0%*** 60*** 0.2** 0.3** 0.2** 0.4** 0.0 *2. ??? *3. cpt-up1.ip.adsl.co.za******* 8.3%*** 60** 20.0* 21.3* 19.2* 42.4** 5.2 *4. cpt-up2.ip.adsl.co.za******* 0.0%*** 60** 20.3* 21.1* 19.4* 37.3** 3.0 *5. cpt-net1.ip.adsl.co.za****** 0.0%*** 60** 19.9* 21.4* 19.3* 54.5** 5.4 *6. optinet.ixp.capetown******** 0.0%*** 60** 22.7* 22.0* 19.8* 53.9** 4.5 *7. bu-ether1.cpt-p-1.optinet.n* 0.0%*** 60** 42.6* 43.7* 41.0* 58.2** 2.9 *8. te0-0-0-0.vic-p-2.optinet.n* 0.0%*** 60** 50.9* 50.9* 47.8* 65.4** 2.6 *9. 197-80-7-15.jhb.mweb.co.za** 0.0%*** 60** 47.6* 48.4* 46.8* 60.7** 2.0 10. bu-ether1.tis-pe-2.optinet.* 0.0%*** 60** 48.0* 49.5* 47.6* 70.3** 4.1 11. bu-ether2.tis-pe-1.optinet.* 0.0%*** 60** 48.1* 49.5* 47.0* 74.8** 5.3 12. 197-80-97-46.jhb.mweb.co.za* 0.0%*** 60** 48.0* 49.0* 47.2* 69.2** 3.5 13. 197-80-247-82.jhb.mweb.co.z* 0.0%*** 60** 40.8* 41.3* 39.8* 57.7** 2.8 14. ???
Based on what I can see it's not IPC that's causing the problem. The latency spike is on a router interface within the Afrihost network, before it breaks out.
So, either (1) that router processor is struggling, (2) the physical interface is oversubscribed at times, (3) shaping/qos/policy is being applied on that interface. My humble opinion.
Glad to hear your latency has picked up.Have you reported this to our CC Team as well?
Been saying that for months already now, to death ears. Could be that the router's out of buffers too - quite a common side effect of heavy QoS as packets start queuing (but quite difficult to address / troubleshoot). Either way, this isn't IPC, this is something INSIDE AH's network. It always has been.
Either way, I'm over this... My fibers (still) hanging outside on my telephone pole, patiently waiting for Telkom to arrive.
Hmmm... very quiet AfriPeeps today. Hope you guys are lambasting the mothership for leaving you all in the lurch.![]()