South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Yip same story here in KZN on capped accounts.had an awesome day, speedwise and playing Diablo. Hit 7 PM tonight and everything went down the drain
Having minimum issues today. lets look at 7-10.
Thanks Afri-peoples
please keep it this way
had an awesome day, speedwise and playing Diablo. Hit 7 PM tonight and everything went down the drain
Full speed on the Japan steam server.![]()
That's good to hear!![]()
Are you connecting to the Japan server specifically?
Yes. I assumed the SA server was trash, cant blame me, so Ive never used it.
Still seems to pull from cortrels.net.afrihost.co.za regardless of selected server.
Ping Test:
ping 197.242.144.102
64 bytes from 197.242.144.102: icmp_req=1 ttl=55 time=97 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=55 time=131 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=55 time=148 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=55 time=211 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=55 time=208 ms
ping 8.8.8.8
64 bytes from 8.8.8.8: icmp_req=1 ttl=51 time=210 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=51 time=160 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=51 time=175 ms
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Trace Test:
traceroute -n 197.242.144.102
1 10.0.0.2 1 ms 1 ms 1 ms
2 Request timed out * * *
3 169.1.5.1 27 ms 81 ms 8 ms
4 169.1.5.1 151 ms 34 ms 8 ms
5 169.1.21.2 24 ms 116 ms
169.1.5.1 121 ms
6 169.1.21.5 91 ms
169.1.5.7 66 ms
169.1.21.2 43 ms
7 197.242.144.1 162 ms
169.1.5.7 35 ms
8 197.242.144.1 126 ms
traceroute -n 8.8.8.8
1 10.0.0.2 1 ms 1 ms
2 Request timed out * *
3 169.1.5.1 8 ms 8 ms
4 169.1.5.1 45 ms 71 ms
5 169.1.21.2 117 ms 105 ms
6 169.1.5.2 27 ms 27 ms
7 8.8.8.8 95 ms 95 ms
DNS Test:
nslookup www.afrihost.com
Name: www.afrihost.com
Address: 104.20.31.244
nslookup www.google.com
Name: www.google.com
Address: 169.1.2.88
nslookup thishouldfail.afrihost.com
** server can't find thisshouldfail.com: NXDOMAIN
And i'm back http downloads don't work again
Uncapped account:
View attachment 436564
Capped Account
View attachment 436570
These test are all from uncapped account.
Pings tests:
View attachment 436566
Again Youtube is not affected
View attachment 436568
Code:Ping Test: ping 197.242.144.102 64 bytes from 197.242.144.102: icmp_req=1 ttl=55 time=97 ms 64 bytes from 197.242.144.102: icmp_req=2 ttl=55 time=131 ms 64 bytes from 197.242.144.102: icmp_req=3 ttl=55 time=148 ms 64 bytes from 197.242.144.102: icmp_req=4 ttl=55 time=211 ms 64 bytes from 197.242.144.102: icmp_req=5 ttl=55 time=208 ms ping 8.8.8.8 64 bytes from 8.8.8.8: icmp_req=1 ttl=51 time=210 ms 64 bytes from 8.8.8.8: icmp_req=2 ttl=51 time=160 ms 64 bytes from 8.8.8.8: icmp_req=3 ttl=51 time=175 ms Request timeout for icmp_seq 4 Request timeout for icmp_seq 5 Trace Test: traceroute -n 197.242.144.102 1 10.0.0.2 1 ms 1 ms 1 ms 2 Request timed out * * * 3 169.1.5.1 27 ms 81 ms 8 ms 4 169.1.5.1 151 ms 34 ms 8 ms 5 169.1.21.2 24 ms 116 ms 169.1.5.1 121 ms 6 169.1.21.5 91 ms 169.1.5.7 66 ms 169.1.21.2 43 ms 7 197.242.144.1 162 ms 169.1.5.7 35 ms 8 197.242.144.1 126 ms traceroute -n 8.8.8.8 1 10.0.0.2 1 ms 1 ms 2 Request timed out * * 3 169.1.5.1 8 ms 8 ms 4 169.1.5.1 45 ms 71 ms 5 169.1.21.2 117 ms 105 ms 6 169.1.5.2 27 ms 27 ms 7 8.8.8.8 95 ms 95 ms DNS Test: nslookup www.afrihost.com Name: www.afrihost.com Address: 104.20.31.244 nslookup www.google.com Name: www.google.com Address: 169.1.2.88 nslookup thishouldfail.afrihost.com ** server can't find thisshouldfail.com: NXDOMAIN
Shaping causes packet lose ? lol ok. xD
And i'm back http downloads don't work again
Uncapped account:
View attachment 436564
Capped Account
View attachment 436570
These test are all from uncapped account.
Pings tests:
View attachment 436566
Again Youtube is not affected
View attachment 436568
Code:Ping Test: ping 197.242.144.102 64 bytes from 197.242.144.102: icmp_req=1 ttl=55 time=97 ms 64 bytes from 197.242.144.102: icmp_req=2 ttl=55 time=131 ms 64 bytes from 197.242.144.102: icmp_req=3 ttl=55 time=148 ms 64 bytes from 197.242.144.102: icmp_req=4 ttl=55 time=211 ms 64 bytes from 197.242.144.102: icmp_req=5 ttl=55 time=208 ms ping 8.8.8.8 64 bytes from 8.8.8.8: icmp_req=1 ttl=51 time=210 ms 64 bytes from 8.8.8.8: icmp_req=2 ttl=51 time=160 ms 64 bytes from 8.8.8.8: icmp_req=3 ttl=51 time=175 ms Request timeout for icmp_seq 4 Request timeout for icmp_seq 5 Trace Test: traceroute -n 197.242.144.102 1 10.0.0.2 1 ms 1 ms 1 ms 2 Request timed out * * * 3 169.1.5.1 27 ms 81 ms 8 ms 4 169.1.5.1 151 ms 34 ms 8 ms 5 169.1.21.2 24 ms 116 ms 169.1.5.1 121 ms 6 169.1.21.5 91 ms 169.1.5.7 66 ms 169.1.21.2 43 ms 7 197.242.144.1 162 ms 169.1.5.7 35 ms 8 197.242.144.1 126 ms traceroute -n 8.8.8.8 1 10.0.0.2 1 ms 1 ms 2 Request timed out * * 3 169.1.5.1 8 ms 8 ms 4 169.1.5.1 45 ms 71 ms 5 169.1.21.2 117 ms 105 ms 6 169.1.5.2 27 ms 27 ms 7 8.8.8.8 95 ms 95 ms DNS Test: nslookup www.afrihost.com Name: www.afrihost.com Address: 104.20.31.244 nslookup www.google.com Name: www.google.com Address: 169.1.2.88 nslookup thishouldfail.afrihost.com ** server can't find thisshouldfail.com: NXDOMAIN
Latency seemed all over the place as well. Please run a ping to bras.afrihost.com the next time it happens.
It could be shaping on your Uncapped account. Does Turbocharge make a difference at all?
I uploaded a large pack of tests last week thursday to your critical care support, and then turbocharging did not help at all. Last night I kinda just gave up and did other things. I just keep getting told do more tests -_-, During the weekend it was more stable though I did not get the time to use it extensively.
Are you still working with our CC Team?When was the last time you guys touched base?
Unfortunately HTTP downloads are also managed when there is network demand.
Hence the slower than normal speeds at various times.