Emissary_Of_Pain
Senior Member
That's the problem ... The tests look good ... but nope ... streaming sucks
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: If you were buying a TV today, which brand would you choose?
Afrihost POC Network - Afrigreen Feedback
- Thread starter AfriGuy
- Start date
- Status
That's the problem ... The tests look good ... but nope ... streaming sucks
Any throughput stats I can check to YouTube?
Last day of the month, 3 hours till caps expire, 99% of South African capped users are going flat out to maximise the cap, and just to top it off most of the Afrihost Uncapped Users will be applying Turbo Boost before they loose that too.
We can't hold it against AH or any other ISP, last day of the month sucks, it is the South African mentality, not network issues.
We can't hold it against AH or any other ISP, last day of the month sucks, it is the South African mentality, not network issues.
Emissary_Of_Pain
Senior Member
ping youtube.com -n 50
Pinging youtube.com [216.58.223.14] with 32 bytes of data:
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Request timed out.
Reply from 216.58.223.14: bytes=32 time=16ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=16ms TTL=57
Request timed out.
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Request timed out.
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Request timed out.
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Request timed out.
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=16ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=19ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Request timed out.
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=21ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=21ms TTL=57
Reply from 216.58.223.14: bytes=32 time=19ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=19ms TTL=57
Reply from 216.58.223.14: bytes=32 time=16ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=19ms TTL=57
Request timed out.
Request timed out.
Ping statistics for 216.58.223.14:
Packets: Sent = 50, Received = 42, Lost = 8 (16% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 21ms, Average = 17ms
tracert youtube.com
Tracing route to youtube.com [216.58.223.14]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 64 ms 92 ms 18 ms 41.170.79.229
4 18 ms 18 ms 17 ms 41.170.79.230
5 40 ms 21 ms 17 ms 41.170.79.236
6 18 ms 20 ms 19 ms google.jb1.napafrica.net [196.46.25.166]
7 23 ms * 18 ms 72.14.237.239
8 36 ms 33 ms * jnb01s07-in-f14.1e100.net [216.58.223.14]
9 17 ms * 19 ms jnb01s07-in-f14.1e100.net [216.58.223.14]
Trace complete.
Pinging youtube.com [216.58.223.14] with 32 bytes of data:
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Request timed out.
Reply from 216.58.223.14: bytes=32 time=16ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=16ms TTL=57
Request timed out.
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Request timed out.
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Request timed out.
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Request timed out.
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=16ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=19ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Request timed out.
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=21ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=21ms TTL=57
Reply from 216.58.223.14: bytes=32 time=19ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=18ms TTL=57
Reply from 216.58.223.14: bytes=32 time=19ms TTL=57
Reply from 216.58.223.14: bytes=32 time=16ms TTL=57
Reply from 216.58.223.14: bytes=32 time=17ms TTL=57
Reply from 216.58.223.14: bytes=32 time=19ms TTL=57
Request timed out.
Request timed out.
Ping statistics for 216.58.223.14:
Packets: Sent = 50, Received = 42, Lost = 8 (16% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 21ms, Average = 17ms
tracert youtube.com
Tracing route to youtube.com [216.58.223.14]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 64 ms 92 ms 18 ms 41.170.79.229
4 18 ms 18 ms 17 ms 41.170.79.230
5 40 ms 21 ms 17 ms 41.170.79.236
6 18 ms 20 ms 19 ms google.jb1.napafrica.net [196.46.25.166]
7 23 ms * 18 ms 72.14.237.239
8 36 ms 33 ms * jnb01s07-in-f14.1e100.net [216.58.223.14]
9 17 ms * 19 ms jnb01s07-in-f14.1e100.net [216.58.223.14]
Trace complete.
Youtube just isn't doing anything really
Tracing route to youtube-ui.l.google.com [216.58.223.14]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 30 ms 32 ms 46 ms ipc-tx-a-access.afrihost.co.za [169.1.1.249]
4 31 ms 30 ms 31 ms ipc-rx-a-access.afrihost.co.za [169.1.1.250]
5 28 ms 28 ms 27 ms 41.170.79.236
6 27 ms 28 ms 28 ms google.jb1.napafrica.net [196.46.25.166]
7 31 ms 30 ms 31 ms 72.14.237.239
8 57 ms 58 ms * jnb01s07-in-f14.1e100.net [216.58.223.14]
9 29 ms 28 ms * jnb01s07-in-f14.1e100.net [216.58.223.14]
10 28 ms * 35 ms jnb01s07-in-f14.1e100.net [216.58.223.14]
Trace complete.
Tracing route to youtube-ui.l.google.com [216.58.223.14]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 30 ms 32 ms 46 ms ipc-tx-a-access.afrihost.co.za [169.1.1.249]
4 31 ms 30 ms 31 ms ipc-rx-a-access.afrihost.co.za [169.1.1.250]
5 28 ms 28 ms 27 ms 41.170.79.236
6 27 ms 28 ms 28 ms google.jb1.napafrica.net [196.46.25.166]
7 31 ms 30 ms 31 ms 72.14.237.239
8 57 ms 58 ms * jnb01s07-in-f14.1e100.net [216.58.223.14]
9 29 ms 28 ms * jnb01s07-in-f14.1e100.net [216.58.223.14]
10 28 ms * 35 ms jnb01s07-in-f14.1e100.net [216.58.223.14]
Trace complete.
standerr
Well-Known Member
Speed has been very poor last couple of days in AfriGreen & MTN.
Current speed test 1.2Mbps on 8Mbps line
Current speed test 1.2Mbps on 8Mbps line
Emissary_Of_Pain
Senior Member
Your Latest Results
Last Result:
Download Speed: 2400 kbps (300 KB/sec transfer rate)
Upload Speed: 836 kbps (104.5 KB/sec transfer rate)
Latency: 17 ms
Jitter: 185 ms
31/08/2015, 21:21:53
Last Result:
Download Speed: 628 kbps (78.5 KB/sec transfer rate)
Upload Speed: 848 kbps (106 KB/sec transfer rate)
Latency: 41 ms
Jitter: 657 ms
31/08/2015, 21:24:01
This is my wonderful 10mbps R1400 per month amazeballs internet ... ...
Well exactly the same things are being said on the VOX forums too, except they are saying definitely a VOX issue.
Apparently Telkom have some issues too that could be compounding things...
Emissary_Of_Pain
Senior Member
Definitely the last month I pay for AH ... ... Actually regretting having paid for this month ... ...
Vulkyrie
Active Member
Still no news on any benefits for the uncapped users? :-(
Last edited:
Nikkel
Expert Member
Thanks a mil for the freebie 100gb again AH!
Emissary_Of_Pain
Senior Member
You can pretty much stop hoping for anything ... ... And by that I mean both benefits and a working network
Vulkyrie
Active Member
Up to now I only had a bad experience on 2 occasions.....in overall the network is functioning perfectly for me. No one is forcing you to use AH.
Morning everyone
I see a few people here mentioning YouTube performance. I was testing between 9pm and 10pm last night. While running a torrent that was peaking around 1MB/s on a 20Mbps line, 720p was running perfectly for me. At times, 1080p needed to be paused for a sec, but otherwise looked pretty good. Without streaming, I was able to max my line out on downloads to between 1.4MB/s and 1.6MB/s so I'm pretty confident that the network should have been capable of good performance in general.
One of my colleagues also said he ran on his normal Afrihost account last night and he founds YouTube streaming to be pretty decent.
Are the any particular similarities between those having a poor experience. Capped or Uncapped? North, South or East? Anything like that we can link those queries together with?
I see a few people here mentioning YouTube performance. I was testing between 9pm and 10pm last night. While running a torrent that was peaking around 1MB/s on a 20Mbps line, 720p was running perfectly for me. At times, 1080p needed to be paused for a sec, but otherwise looked pretty good. Without streaming, I was able to max my line out on downloads to between 1.4MB/s and 1.6MB/s so I'm pretty confident that the network should have been capable of good performance in general.
One of my colleagues also said he ran on his normal Afrihost account last night and he founds YouTube streaming to be pretty decent.
Are the any particular similarities between those having a poor experience. Capped or Uncapped? North, South or East? Anything like that we can link those queries together with?
This will always play a small part but we definitely factor this into our planning to minimise the impact. Generally speaking, while people may have longer sessions to use up bandwidth, they don't increase their overall rate of data transfer so the impact is less that what you might think in terms of realtime demand.
There seems to be a particular misreport when traceroute seems to show inconsistent latency while ping test is solid. We are looking at this with Telkom, but it seems like the pingtest seems to be more indicative of the actual experience (or should be)
- Status