Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
oliverwww said:
Kind of sad that there has been no proper acknowledgement of a serious problem, and even though customers are complaining, nothing has been sorted out in 5 days :(
Click to expand...

:(

Our Team is definitely working on this, and we'll definitely get to the bottom of it and get everyone's performance back to where it should be.
 
Last edited:
NewBiks said:
I've got a question

When a YT video has a low view count should that be impacting the buffering of the video?

http://puu.sh/srPzM/f6a27b4ab2.jpg
Click to expand...

That Video is pulling from the US, not SA. So it is not cached, but if you watch it again now it should pull from a local cache.
Mweb host the Google Cache Cluster that Afrihost uses for YouTube....

Non-authoritative answer:
Name: r3.sn-5hnednlk.googlevideo.com
Addresses: 2a00:1450:400e:20::9
74.125.8.137
 
Hummercellc said:
That Video is pulling from the US, not SA. So it is not cached, but if you watch it again now it should pull from a local cache.
Mweb host the Google Cache Cluster that Afrihost uses for YouTube....

Non-authoritative answer:
Name: r3.sn-5hnednlk.googlevideo.com
Addresses: 2a00:1450:400e:20::9
74.125.8.137
Click to expand...

Thanks a lot of your feedback :)
 
Here we go again :confused:

Tracing route to sip.voip.mweb.net [196.28.95.12]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 17 ms 17 ms 18 ms dbn-up2.ip.adsl.co.za [169.1.5.173]
4 17 ms 17 ms 18 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
5 17 ms 17 ms 17 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
6 77 ms 70 ms 65 ms optinet.ixp.durban [196.10.141.75]
7 126 ms 117 ms 113 ms 197-82-7-2.dbn.mweb.co.za [197.82.7.2]
8 92 ms 83 ms 84 ms te0-0-0-0.vic-p-1.optinet.net [197.84.4.38]
9 102 ms 102 ms 107 ms 201.bu-ether5.vic-pe-2.optinet.net [197.80.7.71]
10 91 ms 84 ms 80 ms 197-81-226-81.jhb.mweb.co.za [197.81.226.81]
11 84 ms * 85 ms 197-81-226-61.jhb.mweb.co.za [197.81.226.61]
12 106 ms 110 ms 117 ms 197-81-229-4.jhb.mweb.co.za [197.81.229.4]
13 107 ms 112 ms 109 ms 197-81-229-23.jhb.mweb.co.za [197.81.229.23]
14 120 ms 115 ms 112 ms sip.voip.mweb.net [196.28.95.12]

Trace complete.
Click to expand...

Tracing route to talk.mweb.net [197.84.140.140]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 17 ms 18 ms 17 ms dbn-up2.ip.adsl.co.za [169.1.5.173]
4 17 ms 17 ms 17 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
5 17 ms 17 ms 18 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
6 83 ms 78 ms 72 ms optinet.ixp.durban [196.10.141.75]
7 106 ms 103 ms 100 ms 197-82-7-2.dbn.mweb.co.za [197.82.7.2]
8 142 ms 157 ms 154 ms te0-0-0-0.vic-p-1.optinet.net [197.84.4.38]
9 169 ms 140 ms 150 ms 197-84-4-101.cpt.mweb.co.za [197.84.4.101]
10 136 ms 98 ms 119 ms te0-0-0-0.cpt-p-1.optinet.net [197.84.4.34]
11 97 ms 103 ms 103 ms te0-7-0-0.cpt-p-2.optinet.net [197.84.4.32]
12 114 ms 101 ms 109 ms 201.te0-0-2-2.cpt-pe-13.optinet.net [197.84.7.45
]
13 149 ms 113 ms 120 ms 197-84-120-20.cpt.mweb.co.za [197.84.120.20]
14 114 ms 108 ms 123 ms talk.mweb.net [197.84.140.140]

Trace complete.
Click to expand...

Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 17 ms 18 ms 18 ms dbn-up2.ip.adsl.co.za [169.1.5.173]
4 17 ms 17 ms 17 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
5 18 ms 17 ms 17 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
6 83 ms 73 ms 71 ms optinet.ixp.durban [196.10.141.75]
7 100 ms 99 ms 97 ms 197-82-7-2.dbn.mweb.co.za [197.82.7.2]
8 106 ms 99 ms 95 ms te0-0-0-0.vic-p-1.optinet.net [197.84.4.38]
9 105 ms 100 ms 96 ms 197-84-4-101.cpt.mweb.co.za [197.84.4.101]
10 102 ms 106 ms 107 ms te0-0-0-0.cpt-p-1.optinet.net [197.84.4.34]
11 169 ms 109 ms 108 ms te0-7-0-0.cpt-p-2.optinet.net [197.84.4.32]
12 100 ms 96 ms 98 ms vl12.cpt-hscore-2.optinet.net [197.84.5.254]
13 124 ms 129 ms 161 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
14 103 ms 103 ms 111 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
Click to expand...

 
NewBiks said:
I've got a question

When a YT video has a low view count should that be impacting the buffering of the video?

http://puu.sh/srPzM/f6a27b4ab2.jpg
Click to expand...

Hummercellc said:
That Video is pulling from the US, not SA. So it is not cached, but if you watch it again now it should pull from a local cache.
Mweb host the Google Cache Cluster that Afrihost uses for YouTube....

Non-authoritative answer:
Name: r3.sn-5hnednlk.googlevideo.com
Addresses: 2a00:1450:400e:20::9
74.125.8.137
Click to expand...

What he said! ;)

NewBiks said:
Thanks a lot of your feedback :)
Click to expand...
 
Tracing route to www.dstv.com [197.80.203.142]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 17 ms 17 ms 17 ms dbn-up2.ip.adsl.co.za [169.1.5.173]
4 17 ms 17 ms 17 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
5 17 ms 17 ms 17 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
6 76 ms 76 ms 66 ms optinet.ixp.durban [196.10.141.75]
7 149 ms 147 ms 146 ms 197-82-7-1.dbn.mweb.co.za [197.82.7.1]
8 98 ms 110 ms 96 ms te0-7-0-1.vic-p-2.optinet.net [197.84.4.44]
9 104 ms 101 ms 96 ms 197-80-7-111.jhb.mweb.co.za [197.80.7.111]
10 107 ms 109 ms 102 ms bu-ether3.mca-pe-1.optinet.net [197.80.4.37]
11 129 ms 104 ms 109 ms 197-80-96-30.jhb.mweb.co.za [197.80.96.30]
12 85 ms 96 ms 95 ms 197-80-206-101.jhb.mweb.co.za [197.80.206.101]
 
Local latency is a piece of **** again...

tracert ql.kreaper.co.za

Tracing route to ql.kreaper.co.za [197.255.148.13]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 14 ms 12 ms 11 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 85 ms 80 ms 92 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 86 ms 84 ms 81 ms adept.ixp.capetown [196.10.140.72]
6 13 ms 13 ms 13 ms v99.bb1.ter.cpt.adept.za.net [196.44.42.154]
7 12 ms 12 ms 12 ms 197.255.148.13

Trace complete.

ping bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
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=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 12ms, Average = 11ms

IJB8RIJ.jpg
 
AfriGenie said:
Which Quake Live Server are you playing on at the moment?
Click to expand...
That was on IS CT Quake Live server. ping is ~18ms then spikes up to 50-60ms only did it on Afrihost account.

Doing the same **** at the moment.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X