Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
Afriman, sure you don't need a side-kick, Afriboy, I can be that guy you know... I have already infiltrated the offices, a free chocolate if you can find out who I am ;)
 
lcbxx said:
Panorama Exchange, 011475 range:
Pinging 105.236.11.129 with 32 bytes of data:
Reply from 105.236.11.129: bytes=32 time=178ms TTL=254

Netflix not breaking 360p on 4Meg line, mostly on 240p and buffers every 2min. Same problem literally every weeknight between 18:30 and 21:30
Click to expand...

Congestion is a bitch :(
 
froot said:
Congestion is a bitch :(
Click to expand...
In all fairness, if I use my FNB Connect account, the pings are 2x as high...

According to Telkom they will gladly assist with more IPC capacity if informed. Perhaps AH can contact Alphonzo and tell inform him of the issue?
 
AfriMan said:
Nobody is receiving less data or paying more than they were previously (or they shouldn't - if you are please PM me).

If your per GB rate is the same or lower than R1,80 - you stay on exactly what you already had previously.
Click to expand...

So where is my "SAVING" or "EXTRA DATA" as promised by Gian in his last mail? (4Gig in my case.... Whoop Whoop)
Is this what he offers after stringing us along for 5 months?(Bundled customers)
Do we still get Mystery Bonus?
 
Beri said:
Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=58 time=50 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=50 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=58 time=51 ms
Request timeout for icmp_seq 4
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=50 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=45 time=214 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=45 time=212 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=45 time=212 ms
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5


Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 2 ms 1 ms 1 ms
2 Request timed out * * *
3 41.181.221.2 43 ms 42 ms 43 ms
4 41.181.221.2 43 ms 42 ms 43 ms
5 41.181.165.1 50 ms 50 ms 54 ms
6 41.181.165.1 43 ms 49 ms 43 ms
7 196.44.31.9 51 ms 50 ms 50 ms
8 196.31.220.6 44 ms 99 ms 43 ms
9 196.31.220.2 45 ms 45 ms 44 ms
10 196.31.63.2 50 ms 53 ms 51 ms
11 197.242.144.1 51 ms 50 ms
196.30.42.1 50 ms
12 197.242.144.1 49 ms


traceroute -n 8.8.8.8

1 192.168.0.1 5 ms
2 Request timed out *
3 41.181.178.6 55 ms
4 41.181.178.5 58 ms
5 41.181.165.1 58 ms
6 209.85.255.7 215 ms
7 Request timed out *
8 Request timed out *


DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102


nslookup www.google.com

Name: www.google.com
Address: 173.194.34.113
Name: www.google.com
Address: 173.194.34.114
Name: www.google.com
Address: 173.194.34.115
Name: www.google.com
Address: 173.194.34.116
Name: www.google.com
Address: 173.194.34.112


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
Click to expand...

Seems like you are still getting that timeout on Hop 2. I think roadcat managed to get this resolved through Telkom, apparently a problem on the exchange since a recent upgrade. I'm thinking this must be the case here as well :(
 
lcbxx said:
Panorama Exchange, 011475 range:
Pinging 105.236.11.129 with 32 bytes of data:
Reply from 105.236.11.129: bytes=32 time=178ms TTL=254
Reply from 105.236.11.129: bytes=32 time=185ms TTL=254
Reply from 105.236.11.129: bytes=32 time=101ms TTL=254
Reply from 105.236.11.129: bytes=32 time=114ms TTL=254
Reply from 105.236.11.129: bytes=32 time=176ms TTL=254
Reply from 105.236.11.129: bytes=32 time=114ms TTL=254
Reply from 105.236.11.129: bytes=32 time=169ms TTL=254
Reply from 105.236.11.129: bytes=32 time=176ms TTL=254
Reply from 105.236.11.129: bytes=32 time=102ms TTL=254
Reply from 105.236.11.129: bytes=32 time=169ms TTL=254
Reply from 105.236.11.129: bytes=32 time=115ms TTL=254
Reply from 105.236.11.129: bytes=32 time=123ms TTL=254
Reply from 105.236.11.129: bytes=32 time=113ms TTL=254
Reply from 105.236.11.129: bytes=32 time=138ms TTL=254
Reply from 105.236.11.129: bytes=32 time=105ms TTL=254
Reply from 105.236.11.129: bytes=32 time=109ms TTL=254
Reply from 105.236.11.129: bytes=32 time=193ms TTL=254
Reply from 105.236.11.129: bytes=32 time=108ms TTL=254
Reply from 105.236.11.129: bytes=32 time=177ms TTL=254
Reply from 105.236.11.129: bytes=32 time=111ms TTL=254

Netflix not breaking 360p on 4Meg line, mostly on 240p and buffers every 2min. Same problem literally every weeknight between 18:30 and 21:30
Click to expand...

That's way too high for what is essentially a local ping. Shouldn't be over 30ms :(
 
Clayman said:
Afriman, sure you don't need a side-kick, Afriboy, I can be that guy you know... I have already infiltrated the offices, a free chocolate if you can find out who I am ;)
Click to expand...

LOL, I already get free chocolate. Gian pays me in Snickers and Dr Pepper :)

Come see me, if you can find me :)
 
AfriMan said:
That's way too high for what is essentially a local ping. Shouldn't be over 30ms :(
Click to expand...
I am glad you agree! Is there anything that can be done to address this? It is not my link to the Exchange that is the problem (Down: 40dB SNR, 5dB Attenuation / UP: 19dB SNR, 3dB Annenuation), it is from there onward.
 
Last edited:
AfriMan said:
Seems like you are still getting that timeout on Hop 2. I think roadcat managed to get this resolved through Telkom, apparently a problem on the exchange since a recent upgrade. I'm thinking this must be the case here as well :(
Click to expand...

So are you going to fix it?
I googled the problem and it could also be the router not allowing pings. Not an expert but you can look for yourself.
 
lcbxx said:
I am glad you agree! Is there anything that can be done to address this? It is not my link to the Exchange that is the problem (Down: 40dB SNR, 5dB Attenuation / UP: 19dB SNR, 3dB Annenuation), it is from there onward.
Click to expand...

Can I see a full traceroute to analyse? I just saw ping to one IP.
 
Beri said:
So are you going to fix it?
I googled the problem and it could also be the router not allowing pings. Not an expert but you can look for yourself.
Click to expand...

We'll need to log a fault with Telkom, as roadcat did, and hopefully we can get them to resolve on their end. I think I should be able to find your number in an old PM somewhere :)
 
AfriMan said:
One local and one international is good. Maybe one to afrihost and the other to 8.8.8.8
Click to expand...
C:\>tracert -d www.afrihost.com

Tracing route to www.afrihost.com [197.242.144.102]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.1
2 131 ms 163 ms 196 ms 105.236.11.129
3 148 ms 154 ms 145 ms 41.181.178.5
4 144 ms 170 ms 165 ms 41.181.165.115
5 104 ms 119 ms 93 ms 196.31.180.4
6 186 ms 183 ms 165 ms 196.44.0.224
7 108 ms 141 ms 147 ms 196.44.31.99
8 117 ms 158 ms 152 ms 196.31.220.8
9 154 ms 133 ms * 196.31.220.25
10 105 ms 95 ms 101 ms 196.31.63.206
11 102 ms 104 ms 117 ms 196.30.42.133
12 106 ms 106 ms 106 ms 197.242.144.102

Trace complete.

C:\>tracert -d 8.8.8.8

Tracing route to 8.8.8.8 over a maximum of 30 hops

1 2 ms 2 ms 1 ms 10.0.0.1
2 121 ms 116 ms 118 ms 105.236.11.129
3 95 ms 98 ms 118 ms 41.181.221.250
4 100 ms 92 ms 95 ms 41.181.165.115
5 118 ms 138 ms 115 ms 196.31.180.4
6 295 ms 280 ms 306 ms 41.181.180.10
7 355 ms 318 ms 303 ms 196.44.31.114
8 324 ms 310 ms 382 ms 196.44.31.156
9 313 ms 270 ms 277 ms 209.212.111.203
10 266 ms 309 ms 351 ms 209.212.99.13
11 * 272 ms 237 ms 209.85.255.78
12 237 ms 235 ms 257 ms 209.85.253.94
13 251 ms 228 ms 215 ms 72.14.232.134
14 228 ms 211 ms 219 ms 216.239.47.83
15 * * * Request timed out.
16 262 ms 270 ms 284 ms 8.8.8.8

Trace complete.
 
lcbxx said:
1 1 ms 1 ms 1 ms 10.0.0.1
2 131 ms 163 ms 196 ms 105.236.11.129

1 2 ms 2 ms 1 ms 10.0.0.1
2 121 ms 116 ms 118 ms 105.236.11.129
Click to expand...

Yup, that's your problem.... congestion :(
Although it's not "that" bad. I usually got whacked with 1000ms pings when I had congestion.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X