-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: What is your primary source of drinking water?
- Status
Try change your port number in your torrent program.
My latency looks to be returning to normal and throughput's coming up slowly but surely, which is good news 
How are you guys results looking?
How are you guys results looking?
Don't know - on a different ISP account atm; I'll check l8tr.My latency looks to be returning to normal and throughput's coming up slowly but surely, which is good news
How are you guys results looking?
Http is fine.
Hhhmm, OK. If shaping was being applied then HTTP would be affected too.
Perhaps try another torrent client to test?
NewBiks
Well-Known Member
My latency looks to be returning to normal and throughput's coming up slowly but surely, which is good news
How are you guys results looking?
Yea no it's still pretty bad
Any tests available for me to look at?
NewBiks
Well-Known Member
The last 2 results look to be getting better.
Can you run a ping on that 3rd hop to see the results? IPC is definitely normalising on our end.
No IPC is still borked and unstable beyond bras:Alrighty
Tracing route to ql.kreaper.co.za [196.44.45.98]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 * 35 ms 35 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 77 ms 77 ms 78 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 14 ms 11 ms 12 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 15 ms 12 ms 12 ms adept.ct1.napafrica.net [196.10.140.72]
7 18 ms 15 ms 14 ms v498.pe0.adc.adept.za.net [196.44.40.193]
8 48 ms 44 ms 48 ms g0-9.bb3.adc.adept.za.net [196.44.40.118]
9 16 ms 14 ms 15 ms e1.fw0.adc.adept.za.net [196.44.32.197]
10 77 ms 77 ms 76 ms ql.kreaper.co.za [196.44.45.98]
Trace complete.
Pinging 169.1.5.105 with 32 bytes of data:
Reply from 169.1.5.105: bytes=32 time=26ms TTL=58
Reply from 169.1.5.105: bytes=32 time=49ms TTL=58
Reply from 169.1.5.105: bytes=32 time=42ms TTL=58
Reply from 169.1.5.105: bytes=32 time=42ms TTL=58
Reply from 169.1.5.105: bytes=32 time=47ms TTL=58
Reply from 169.1.5.105: bytes=32 time=36ms TTL=58
Reply from 169.1.5.105: bytes=32 time=39ms TTL=58
Reply from 169.1.5.105: bytes=32 time=46ms TTL=58
Reply from 169.1.5.105: bytes=32 time=54ms TTL=58
Reply from 169.1.5.105: bytes=32 time=47ms TTL=58
Reply from 169.1.5.105: bytes=32 time=41ms TTL=58
Reply from 169.1.5.105: bytes=32 time=41ms TTL=58
Reply from 169.1.5.105: bytes=32 time=39ms TTL=58
Reply from 169.1.5.105: bytes=32 time=45ms TTL=58
Reply from 169.1.5.105: bytes=32 time=40ms TTL=58
Reply from 169.1.5.105: bytes=32 time=44ms TTL=58
Reply from 169.1.5.105: bytes=32 time=60ms TTL=58
Reply from 169.1.5.105: bytes=32 time=41ms TTL=58
Ping statistics for 169.1.5.105:
Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 60ms, Average = 43ms
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 19, Received = 19, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 20ms, Average = 12ms
NewBiks
Well-Known Member
3rd hop resolves to 169.1.5.93
http://puu.sh/q8gYp/87d9705d42.png
YouTube line usage:
This is while trying to run a 720p vid
http://puu.sh/q8gJh/ec4a0416b5.png
Last edited:
Still quite erratic here
Perhaps try a reboot and open a new session?Otherwise what does a ping to bras.afrihost.com look like?
NewBiks
Well-Known Member
Still quite erratic here
Otherwise what does a ping to bras.afrihost.com look like?
Before the reboot
http://puu.sh/q8hlH/4bba841947.png
Everything seems fine but its not
ps. Hate that I have to a reboot in hopes that the issue will be fixed
1.1-1.4mbit on Youtube. I am seeing about 1.3-1.6mbit on torrents on a line max of 1.8mbit.
Before the reboot
http://puu.sh/q8hlH/4bba841947.png
Everything seems fine but its not
ps. Hate that I have to a reboot in hopes that the issue will be fixed
Just confirmed with our network team that the issues are definitely resolved on our end, but we're still monitoring traffic closely.
Here's a test I ran a few mins back, my experience has pretty much normalised.
Code:
Start: Wed Jul 20 18:35:17 2016
HOST: hydra Loss% Snt Last Avg Best Wrst StDev
1.|-- router.asus.com 0.0% 10 0.4 0.4 0.3 0.5 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3.|-- cpt-up1.ip.adsl.co.za 50.0% 10 33.5 53.2 25.4 75.0 22.2
4.|-- cpt-up2.ip.adsl.co.za 0.0% 10 40.9 46.6 14.1 82.1 23.3
5.|-- cpt-net1.ip.adsl.co.za 0.0% 10 66.0 92.3 66.0 129.8 23.5
6.|-- 41.164.52.40 0.0% 10 71.7 96.3 71.4 150.3 27.8
7.|-- 172.18.1.162 0.0% 10 97.5 114.2 96.7 140.6 18.3
8.|-- 72.14.194.206 0.0% 10 94.0 98.1 68.0 134.6 22.4
9.|-- 72.14.237.239 10.0% 10 127.3 122.1 97.7 177.1 27.2
10.|-- jnb01s07-in-f3.1e100.net 10.0% 10 98.1 113.6 98.1 139.3 18.3- Status