diepeterpan
Well-Known Member
Mine AFRIHOST ADSL is also better, but maybe it is because of the time "6:46am", let's see how long it remains this good.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
It seems MyBB speedtest is unshaped and yet http and torrents are shaped/throttled at 120kB
International:
Test conducted on 11 November 2012 07:10:54 AM
Download Speed: 3503 kbps (437.9 KB/sec transfer rate)
Upload Speed: 410 kbps (51.3 KB/sec transfer rate)
Latency: 229 ms
Again, let me repeat: Where Speedtest.net claim you are has absolutely nothing to do with the quality of Afrihost's network or what speed, latency or quality you get out of your internet connection. It is merely where Speedtest.net claim you are. Nothing else.
if it can stay like this all day (maybe lower latency) i'll be happy
Test conducted on 11 November 2012 07:48
Download Speed: 3069 kbps (383.6 KB/sec transfer rate)
Upload Speed: 411 kbps (51.4 KB/sec transfer rate)
Latency: 237 ms
Not at all. It uses geoip info to determine location based on your ip.Aren't the speedtest 'guesses' an indication of Afrihost's routing?







C:\Windows\system32>pathping www.escapistmagazine.com
Tracing route to www2.tmserv.net [209.34.224.72]
over a maximum of 30 hops:
0 JadeX64 [10.10.10.10]
1 . [10.10.10.1]
2 105-236-3-129-esr-lo.mtnbusiness.co.za [105.236.3.129]
3 ipc-recieve-jh-1a.za.mtnbusiness.net [41.181.178.5]
4 qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
6 am-cr-2.nl--am-tpr-1.nl-a.mtn.net [209.212.111.218]
7 xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.89]
8 4.69.162.145
9 ae-56-221.ebr2.Amsterdam1.Level3.net [4.69.153.201]
10 ae-46-46.ebr2.London1.Level3.net [4.69.143.74]
11 ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66]
12 ae-10-10.ebr2.Washington12.Level3.net [4.69.148.50]
13 ae-5-5.ebr2.Washington1.Level3.net [4.69.143.221]
14 ae-6-6.car2.Raleigh1.Level3.net [4.69.132.177]
15 ae-11-11.car1.Raleigh1.Level3.net [4.69.132.173]
16 PEAK-10.car1.Raleigh1.Level3.net [4.71.160.50]
17 v13.rd1.ral.peak10.net [66.129.104.25]
18 www2.tmserv.net [209.34.224.72]
19 * * *
Computing statistics for 450 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 JadeX64 [10.10.10.10]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% . [10.10.10.1]
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0% 105-236-3-129-esr-lo.mtnbusiness.co.za [105.236.3.129]
0/ 100 = 0% |
3 13ms 0/ 100 = 0% 0/ 100 = 0% ipc-recieve-jh-1a.za.mtnbusiness.net [41.181.178.5]
0/ 100 = 0% |
4 13ms 0/ 100 = 0% 0/ 100 = 0% qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
0/ 100 = 0% |
5 12ms 0/ 100 = 0% 0/ 100 = 0% jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
0/ 100 = 0% |
6 192ms 0/ 100 = 0% 0/ 100 = 0% am-cr-2.nl--am-tpr-1.nl-a.mtn.net[209.212.111.218]
0/ 100 = 0% |
7 204ms 0/ 100 = 0% 0/ 100 = 0% xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.89]
0/ 100 = 0% |
8 188ms 0/ 100 = 0% 0/ 100 = 0% 4.69.162.145
0/ 100 = 0% |
9 184ms 0/ 100 = 0% 0/ 100 = 0% ae-56-221.ebr2.Amsterdam1.Level3.net [4.69.153.201]
0/ 100 = 0% |
10 201ms 0/ 100 = 0% 0/ 100 = 0% ae-46-46.ebr2.London1.Level3.net [4.69.143.74]
0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% ae-41-41.ebr1.NewYork1.Level3.net[4.69.137.66]
0/ 100 = 0% |
12 279ms 0/ 100 = 0% 0/ 100 = 0% ae-10-10.ebr2.Washington12.Level3.net [4.69.148.50]
0/ 100 = 0% |
13 275ms 0/ 100 = 0% 0/ 100 = 0% ae-5-5.ebr2.Washington1.Level3.net [4.69.143.221]
0/ 100 = 0% |
14 301ms 0/ 100 = 0% 0/ 100 = 0% ae-6-6.car2.Raleigh1.Level3.net [4.69.132.177]
0/ 100 = 0% |
15 303ms 0/ 100 = 0% 0/ 100 = 0% ae-11-11.car1.Raleigh1.Level3.net[4.69.132.173]
0/ 100 = 0% |
16 287ms 0/ 100 = 0% 0/ 100 = 0% PEAK-10.car1.Raleigh1.Level3.net [4.71.160.50]
0/ 100 = 0% |
17 274ms 0/ 100 = 0% 0/ 100 = 0% v13.rd1.ral.peak10.net [66.129.104.25]
0/ 100 = 0% |
18 281ms 0/ 100 = 0% 0/ 100 = 0% www2.tmserv.net [209.34.224.72]
Trace complete.
C:\Windows\system32>
Just DCed from D3, this is making it impossible to play D3 with expected DCs.
I sort of disagree. Whenever speedtest's location suddenly is reported as somewhere else, its a pretty good indication that Afrihost have just made some sort of adjustment or change.
I'm in Durban, and since the move to MTN I've been reported as being in Jhb most of the time. Sometimes it has reported that my location is in London, which has generally coincided with bad performance.
Don't get me wrong, I'm getting the same performance as when I was reported as being in Jhb, but I'm just saying things are getting somewhere.
I'm pretty sure the location changes are due to Afrihost's tinkering.
Aren't the speedtest 'guesses' an indication of Afrihost's routing?
No, it is not. Speedtest.net guess solely based on the IP address. Sorry to burst your bubble.
Three things for you to read about.
Confirmation bias (also called confirmatory bias or myside bias) is a tendency of people to favor information that confirms their beliefs or hypotheses.[Note 1][1] People display this bias when they gather or remember information selectively, or when they interpret it in a biased way.
"Correlation does not imply causation" is a phrase used in science and statistics to emphasize that a correlation between two variables does not necessarily imply that one causes the other.
Sample size determination is the act of choosing the number of observations or replicates to include in a statistical sample. The sample size is an important feature of any empirical study in which the goal is to make inferences about a population from a sample.
You can of course also refuse to read any of those things and go on with your religious belief that Speedtest.net's guesses based on your IP address has anything at all to do with Afrihost's service.
Yes. Speedtest.net's guesses got better for you. That still has absolutely nothing to do with the performance of Afrihost. Nothing. Nada. Zip. Nil.
And you base this irrational belief on exactly what?
No. They have nothing at all to do with networking, your network performance or routing. They are 100% based on the IP address alone. They are a product of your IP address and Speedtest.net's database for guessing geographical locations based on IP addresses.