Johnatan56
Honorary Master
272ms latency EUW again. That seems to be the norm for weekday evenings and entire weekends.
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Which is the most hair-raising South African mountain pass you've driven?
Afrihost Capped DSL Feedback
- Thread starter AfriFella
- Start date
squish0601
Well-Known Member
- Joined
- Nov 30, 2016
- Messages
- 113
- Reaction score
- 1
Why do you keep putting yourself through this?
Its just unneeded stress. Just give notice and pick a different company. At this rate any other is better
electrofreeze
Expert Member
it takes about 1min for the forum to load with ah
Johnatan56
Honorary Master
I am currently trying to convince the account holder to change, will probably be on a new package beginning next month.
joshsparkie
Well-Known Member
Getting terrible pings and speeds this evening on Cape Town IPC and 100mbps OpenServe FTTH via Afrihost unshaped capped
Johnatan56
Honorary Master
Constant buffering on 720p even. I should be able to handle 3+ concurrent 1080p streams on this line.
savage
Expert Member
At this rate, I'll go help to dig the trench to get my fiber in for my Metro Ethernet.
Can't wait until I'm finished with this pathetic excuse for an ISP.
Can't wait until I'm finished with this pathetic excuse for an ISP.
Sopbeen
Senior Member
- Joined
- Jul 6, 2007
- Messages
- 628
- Reaction score
- 497
Same setup, same problems here. Actually started precisely 5 mins before the spacex launch. Couldn't believe it. I had to scramble to switch to my vox account to view the launch scrub. The quality went from 1080p streaming to 360p and less with it buffering on 360p constantly.
I would call this a R1 testing fail. Nice bandwidth to burn for downloads, but I have to switch to Vox for anything else.
squish0601
Well-Known Member
- Joined
- Nov 30, 2016
- Messages
- 113
- Reaction score
- 1
Lol. Had the same problem. Usually I pay for it but when we switch tot Ah I made him pay for it. Switching is just such a mission.
I'm just glad its finally done.
Johnatan56
Honorary Master
Lovely that there were issues already at midday today, buffering on 360p even once we hit 1pm. Also the exact time the account holder was using the net.
And really? You messed up <br>?
I guess the world of tanks problem still isn't fixed?
WOT EU1:
Pinging ed-sl-a115.fe.core.pw [92.223.20.115] with 32 bytes of data:
Reply from 92.223.20.115: bytes=32 time=289ms TTL=46
Reply from 92.223.20.115: bytes=32 time=321ms TTL=46
Reply from 92.223.20.115: bytes=32 time=286ms TTL=46
Reply from 92.223.20.115: bytes=32 time=305ms TTL=46
Reply from 92.223.20.115: bytes=32 time=290ms TTL=46
Reply from 92.223.20.115: bytes=32 time=281ms TTL=46
Reply from 92.223.20.115: bytes=32 time=309ms TTL=46
Reply from 92.223.20.115: bytes=32 time=302ms TTL=46
Reply from 92.223.20.115: bytes=32 time=301ms TTL=46
Request timed out.
Reply from 92.223.20.115: bytes=32 time=298ms TTL=46
Reply from 92.223.20.115: bytes=32 time=283ms TTL=46
Reply from 92.223.20.115: bytes=32 time=299ms TTL=46
Reply from 92.223.20.115: bytes=32 time=298ms TTL=46
Reply from 92.223.20.115: bytes=32 time=307ms TTL=46
Reply from 92.223.20.115: bytes=32 time=321ms TTL=46
Reply from 92.223.20.115: bytes=32 time=317ms TTL=46
Reply from 92.223.20.115: bytes=32 time=303ms TTL=46
Yes there's packet loss even.
Tracing route to ed-sl-a115.fe.core.pw [92.223.20.115]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 141 ms 133 ms 125 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
4 22 ms 19 ms 20 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 20 ms 20 ms 20 ms 41.164.52.40
6 55 ms 54 ms 51 ms ix-ae-7-0.tcore1.KLT-Cape-Town.as6453.net [41.206.164.53]
7 186 ms 181 ms 181 ms if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.109]
8 182 ms 182 ms 182 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
9 176 ms 180 ms 176 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
10 175 ms 175 ms 175 ms if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
11 176 ms 175 ms * if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
12 176 ms 177 ms 183 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
13 279 ms 282 ms 304 ms be3040.ccr21.lon01.atlas.cogentco.com [130.117.15.177]
14 175 ms 175 ms 175 ms be2868.ccr41.lon13.atlas.cogentco.com [154.54.57.153]
15 227 ms 219 ms 228 ms be12194.ccr41.ams03.atlas.cogentco.com [154.54.56.94]
16 177 ms 177 ms 177 ms be2412.rcr21.b038092-0.ams03.atlas.cogentco.com [154.54.37.98]
17 183 ms 183 ms 184 ms 149.11.65.26
18 183 ms 183 ms 184 ms ed-n5596up-fe-1-vl241.fe.core.pw [92.223.112.163]
19 277 ms 301 ms 293 ms ed-sl-a115.fe.core.pw [92.223.20.115]
Can I ask what "cpt-up2.ip.adsl.co.za" is? Because even pinging it gives me terrible ping:
Pinging cpt-up2.ip.adsl.co.za [169.1.5.106] with 32 bytes of data:
Reply from 169.1.5.106: bytes=32 time=110ms TTL=59
Reply from 169.1.5.106: bytes=32 time=177ms TTL=59
Reply from 169.1.5.106: bytes=32 time=120ms TTL=59
Reply from 169.1.5.106: bytes=32 time=131ms TTL=59
Reply from 169.1.5.106: bytes=32 time=135ms TTL=59
Reply from 169.1.5.106: bytes=32 time=152ms TTL=59
Reply from 169.1.5.106: bytes=32 time=199ms TTL=59
Reply from 169.1.5.106: bytes=32 time=174ms TTL=59
Reply from 169.1.5.106: bytes=32 time=204ms TTL=59
Reply from 169.1.5.106: bytes=32 time=134ms TTL=59
Reply from 169.1.5.106: bytes=32 time=148ms TTL=59
Reply from 169.1.5.106: bytes=32 time=140ms TTL=59
Reply from 169.1.5.106: bytes=32 time=129ms TTL=59
*shrugs*
WOT EU1:
Pinging ed-sl-a115.fe.core.pw [92.223.20.115] with 32 bytes of data:
Reply from 92.223.20.115: bytes=32 time=289ms TTL=46
Reply from 92.223.20.115: bytes=32 time=321ms TTL=46
Reply from 92.223.20.115: bytes=32 time=286ms TTL=46
Reply from 92.223.20.115: bytes=32 time=305ms TTL=46
Reply from 92.223.20.115: bytes=32 time=290ms TTL=46
Reply from 92.223.20.115: bytes=32 time=281ms TTL=46
Reply from 92.223.20.115: bytes=32 time=309ms TTL=46
Reply from 92.223.20.115: bytes=32 time=302ms TTL=46
Reply from 92.223.20.115: bytes=32 time=301ms TTL=46
Request timed out.
Reply from 92.223.20.115: bytes=32 time=298ms TTL=46
Reply from 92.223.20.115: bytes=32 time=283ms TTL=46
Reply from 92.223.20.115: bytes=32 time=299ms TTL=46
Reply from 92.223.20.115: bytes=32 time=298ms TTL=46
Reply from 92.223.20.115: bytes=32 time=307ms TTL=46
Reply from 92.223.20.115: bytes=32 time=321ms TTL=46
Reply from 92.223.20.115: bytes=32 time=317ms TTL=46
Reply from 92.223.20.115: bytes=32 time=303ms TTL=46
Yes there's packet loss even.
Tracing route to ed-sl-a115.fe.core.pw [92.223.20.115]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 141 ms 133 ms 125 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
4 22 ms 19 ms 20 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 20 ms 20 ms 20 ms 41.164.52.40
6 55 ms 54 ms 51 ms ix-ae-7-0.tcore1.KLT-Cape-Town.as6453.net [41.206.164.53]
7 186 ms 181 ms 181 ms if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.109]
8 182 ms 182 ms 182 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
9 176 ms 180 ms 176 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
10 175 ms 175 ms 175 ms if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
11 176 ms 175 ms * if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
12 176 ms 177 ms 183 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
13 279 ms 282 ms 304 ms be3040.ccr21.lon01.atlas.cogentco.com [130.117.15.177]
14 175 ms 175 ms 175 ms be2868.ccr41.lon13.atlas.cogentco.com [154.54.57.153]
15 227 ms 219 ms 228 ms be12194.ccr41.ams03.atlas.cogentco.com [154.54.56.94]
16 177 ms 177 ms 177 ms be2412.rcr21.b038092-0.ams03.atlas.cogentco.com [154.54.37.98]
17 183 ms 183 ms 184 ms 149.11.65.26
18 183 ms 183 ms 184 ms ed-n5596up-fe-1-vl241.fe.core.pw [92.223.112.163]
19 277 ms 301 ms 293 ms ed-sl-a115.fe.core.pw [92.223.20.115]
Can I ask what "cpt-up2.ip.adsl.co.za" is? Because even pinging it gives me terrible ping:
Pinging cpt-up2.ip.adsl.co.za [169.1.5.106] with 32 bytes of data:
Reply from 169.1.5.106: bytes=32 time=110ms TTL=59
Reply from 169.1.5.106: bytes=32 time=177ms TTL=59
Reply from 169.1.5.106: bytes=32 time=120ms TTL=59
Reply from 169.1.5.106: bytes=32 time=131ms TTL=59
Reply from 169.1.5.106: bytes=32 time=135ms TTL=59
Reply from 169.1.5.106: bytes=32 time=152ms TTL=59
Reply from 169.1.5.106: bytes=32 time=199ms TTL=59
Reply from 169.1.5.106: bytes=32 time=174ms TTL=59
Reply from 169.1.5.106: bytes=32 time=204ms TTL=59
Reply from 169.1.5.106: bytes=32 time=134ms TTL=59
Reply from 169.1.5.106: bytes=32 time=148ms TTL=59
Reply from 169.1.5.106: bytes=32 time=140ms TTL=59
Reply from 169.1.5.106: bytes=32 time=129ms TTL=59
*shrugs*
Johnatan56
Honorary Master
I think it's the IPC from OpenServe > Afrihost network.
DeatheCore
Senior Member
Twitch performance is quite bad again this evening.
It started strong, then performance leveled out at a low rate. Lots of buffering.
Pings are good, throughput is bad.
It started strong, then performance leveled out at a low rate. Lots of buffering.
Pings are good, throughput is bad.
Last edited:
Morning everyone
We're passing all your feedback back to the network team. Seems like a few people from the Cape still having issues. Thank you for sharing your results and tests.
Let's hope we can improve your experience soon
We're passing all your feedback back to the network team. Seems like a few people from the Cape still having issues. Thank you for sharing your results and tests.
Let's hope we can improve your experience soon
Twitch performance is quite bad again this evening.
It started strong, then performance leveled out at a low rate. Lots of buffering.
Pings are good, throughput is bad.
View attachment 419058
Your latency is pretty good, so that's weird. Throughput without latency issues wouldn't indicate that international was congested, but perhaps an issue on Twitch ( if other services were running well).
Do you have an example stream we can test?
As far as I am aware performance has been good. From your tests it looks like everything is fine until we reach the hosting network, and then latency seems to spike
Lovely that there were issues already at midday today, buffering on 360p even once we hit 1pm. Also the exact time the account holder was using the net.
View attachment 418958
And really? You messed up <br>?
View attachment 418960
Thanks for bringing that to our attention. We'll definitely correct that.
Iam very sorry to hear that you're cancelling with us. I sincerely wish you all the best for the future
The might have been a huge demand for that content. Demand was fairly consistent in the south throughout the day, but we did see it peak around 16:00 when the launch started - more or less
That's not cool! Is your DSL line sync intermittently dropping, or just the throughput?
I got a reply from your help desk stating that everything is ok on my line and now my router is apparently the problem.
My Router (DSL2750U) is rock solid.
I shouldn't be struggling to watch youtube clips, imdb trailers or some clips on FB... I never even had this problem on my 2Meg line with Telkom, why is 4Meg such an issue?
Johnatan56
Honorary Master
Look at hop 7 which is still in Cape Town, 170ms. How is there not something wrong there.