Well it didn't last long. I'm shaped to 50% Download/ 50% P2P. It still pretty good though.
Same here also back at 50%
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Well it didn't last long. I'm shaped to 50% Download/ 50% P2P. It still pretty good though.
Same here also back at 50%![]()
Down to 18.8% Download/ 6.25% P2P....
shaping removed from about midnight last night. Yay.

PING google.com (74.125.233.36) 56(84) bytes of data.
64 bytes from jnb01s01-in-f4.1e100.net (74.125.233.36): icmp_req=1 ttl=53 time=216 ms
64 bytes from jnb01s01-in-f4.1e100.net (74.125.233.36): icmp_req=2 ttl=53 time=33.7 ms
64 bytes from jnb01s01-in-f4.1e100.net (74.125.233.36): icmp_req=3 ttl=53 time=103 ms
64 bytes from jnb01s01-in-f4.1e100.net (74.125.233.36): icmp_req=4 ttl=53 time=499 ms
64 bytes from jnb01s01-in-f4.1e100.net (74.125.233.36): icmp_req=5 ttl=53 time=315 ms
64 bytes from 74.125.233.36: icmp_req=6 ttl=53 time=269 ms
64 bytes from jnb01s01-in-f4.1e100.net (74.125.233.36): icmp_req=7 ttl=53 time=277 ms
64 bytes from jnb01s01-in-f4.1e100.net (74.125.233.36): icmp_req=8 ttl=53 time=565 ms
64 bytes from jnb01s01-in-f4.1e100.net (74.125.233.36): icmp_req=9 ttl=53 time=262 ms
64 bytes from jnb01s01-in-f4.1e100.net (74.125.233.36): icmp_req=10 ttl=53 time=246 ms
64 bytes from jnb01s01-in-f4.1e100.net (74.125.233.36): icmp_req=11 ttl=53 time=533 ms
64 bytes from jnb01s01-in-f4.1e100.net (74.125.233.36): icmp_req=12 ttl=53 time=364 ms
64 bytes from jnb01s01-in-f4.1e100.net (74.125.233.36): icmp_req=13 ttl=53 time=463 ms
64 bytes from jnb01s01-in-f4.1e100.net (74.125.233.36): icmp_req=14 ttl=53 time=334 ms
64 bytes from jnb01s01-in-f4.1e100.net (74.125.233.36): icmp_req=15 ttl=53 time=394 ms
64 bytes from jnb01s01-in-f4.1e100.net (74.125.233.36): icmp_req=16 ttl=53 time=588 ms
64 bytes from jnb01s01-in-f4.1e100.net (74.125.233.36): icmp_req=17 ttl=53 time=336 ms
64 bytes from jnb01s01-in-f4.1e100.net (74.125.233.36): icmp_req=18 ttl=53 time=164 ms
64 bytes from jnb01s01-in-f4.1e100.net (74.125.233.36): icmp_req=19 ttl=53 time=309 ms
64 bytes from jnb01s01-in-f4.1e100.net (74.125.233.36): icmp_req=20 ttl=53 time=354 ms
^C
--- google.com ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 38324ms
rtt min/avg/max/mdev = 33.728/331.675/588.389/143.860 ms
[silvercode@silvercode-home:local/bin]$ tracepath google.com (24-09 12:31)
1: silvercode-home.local 0.124ms pmtu 1500
1: 192.168.1.1 1.748ms
1: 192.168.1.1 2.094ms
2: 105-236-148-222.access.mtnbusiness.co.za 1.975ms pmtu 1492
2: 105-236-8-193-esr-lo.mtnbusiness.co.za 369.801ms
3: ipc-send-tb-3a.mtnbusiness.net 231.890ms asymm 7
4: tb-dca-2.za--qux-c.za.mtnbusiness.net 225.992ms asymm 6
5: compj-cpt-1.mtnns.net 448.636ms asymm 6
6: ct-cr-2.za--tb-cr-1.za.mtnns.net 320.886ms asymm 7
7: ct-cr-2.za--rb-cr-1.za.mtnns.net 435.878ms asymm 8
8: 41.181.139.109 212.130ms asymm 10
9: no reply
10: no reply
11: no reply
12: no reply
13: no reply
14: no reply
15: no reply
16: no reply
17: no reply
18: no reply
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
31: no reply
Too many hops: pmtu 1492
Resume: pmtu 1492
ugh. Didn't last long. Shaping Policy: 25% Download/ 12.5% P2P. Surely the recent pattern of shaping is more than just a temporary capacity issue?
Isn't this a graph of JINX?
I'm sure if we could see one of AH JHB IPC it would be a different picture.
The shaping today makes me think that AH have more consumers than businesses, in which case, an IPC upgrade is required.
Even if shaped, streaming is supposed to go at 100% - right?
Youtube was fine this morning, but now it's completely borked.![]()
4mb account...
Trying to watch twitch on anything but low is painful![]()