Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
caroper said:
My pleasure, you may want to pass them the Local Trace too:

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

1 <1 ms 1 ms 1 ms www.routerlogin.com [192.168.0.200]
2 * * * Request timed out.
3 57 ms 69 ms 60 ms 41.181.53.213
4 9 ms 8 ms 8 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
5 53 ms 8 ms 8 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
6 8 ms 45 ms 8 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 30 ms 31 ms 30 ms pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66]
8 29 ms 30 ms 30 ms jh-cr-2.za--jh-cr-1.za-a.mtnns.net [196.44.31.255]
9 46 ms 68 ms 77 ms 196.44.31.99
10 29 ms 29 ms 32 ms 196.30.1.39
11 58 ms 60 ms 61 ms 196.31.220.21
12 30 ms 30 ms 31 ms 196.31.63.202
13 83 ms 30 ms 30 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
14 30 ms 30 ms 30 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.
Click to expand...

Let's hope we can find the issue here. Seems to be intermittent.
 
Is it not the same issue as last, where the profiles in the equipment was not applied properly?
 
nicki said:
Is it not the same issue as last, where the profiles in the equipment was not applied properly?
Click to expand...

No, I don't think so. Although the core issues was traffic classification (then) the symptoms we saw was traffic being smashed because we weren't controlling it properly. What we're seeing now is that traffic consumption is well within range but we're seeing intermittent latency. We're still investigating to try to reliably replicate this so we can isolate the cause.
 
Are you sure your system reporting IPC usage is accurate and not maybe missing some traffic?
 
AfriGenie said:
We don't seem to be having any similar issues in the East at the moment, would you be able to post a speedtest as well as a Traceroute to Afrihost.com and possibly the H1Z1 server? That will help a lot in being able to figure out where your issue is starting.
Click to expand...

Thanks will do tonight when i get home
 
nicki said:
Are you sure your system reporting IPC usage is accurate and not maybe missing some traffic?
Click to expand...

Definitely, the reports come directly out of the IPC so we know exactly what traffic is going out vs available capacity. Our shaping device (or devices more accurately) identify traffic according to classifications, but will also still report "Other" traffic if not classified.
 
problem seems to be resolved for how i dont know,though this packet loss isnt working for me anymore :/ as i play battlefield ..
 
djbrendan said:
problem seems to be resolved for how i dont know,though this packet loss isnt working for me anymore :/ as i play battlefield ..
Click to expand...

Yep, packet loss is still present. So only one of the many issues resolved....
 
Any news Afriman? Im also in CT southern Suburbs and my ping was over 200 last night : / Couldnt game online at all...
 
Masik3R said:
Yep, packet loss is still present. So only one of the many issues resolved....
Click to expand...

We are making definite progress towards resolving this issue permanently, I'll continue to monitor from my side and keep you guys updated.
 
djbrendan said:
Does this include packet loss that has been on the AH network for the last few months
Click to expand...

The issue that started on Friday evening specifically only started on Friday evening, if you experienced any latency or packet loss before then we'll need to look into this as an individual case.

Are you seeing packet loss in general or only during specific times? To which sites or services are you noticing this?
 
Can someone at Afrihost please explain the following tests for me. This all done on an Afrihost Capped account within 2 hours from the same line and router.

TRACEROUTES:

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

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 93 ms 88 ms 44 ms 41.181.201.93
4 34 ms 34 ms 35 ms 41.181.201.94
5 41 ms 62 ms 41 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
6 43 ms 42 ms 41 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 61 ms 62 ms 65 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
8 63 ms 63 ms 63 ms jh-cr-2.za--jh-cr-1.za-a.mtnns.net [196.44.31.255]
9 62 ms 62 ms 72 ms 196.44.31.99
10 62 ms 62 ms 64 ms 196.31.220.6
11 55 ms 55 ms 54 ms 196.31.220.23
12 56 ms 56 ms 55 ms 196.31.63.206
13 55 ms 55 ms 54 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
14 62 ms 61 ms 61 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.


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

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 102 ms 83 ms 81 ms 41.181.221.253
4 34 ms 35 ms 34 ms 41.181.221.254
5 34 ms 34 ms 34 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
6 79 ms 43 ms 41 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 55 ms 55 ms 55 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
8 63 ms 63 ms 62 ms jh-cr-2.za--jh-cr-1.za-a.mtnns.net [196.44.31.255]
9 62 ms 78 ms 62 ms 196.44.31.99
10 55 ms 56 ms 56 ms 196.31.220.6
11 55 ms 55 ms 56 ms 196.31.220.23
12 55 ms 56 ms 54 ms 196.31.63.206
13 58 ms 59 ms 55 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
14 63 ms 62 ms 62 ms www.afrihost.com [197.242.144.102]

Trace complete.


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

1 <1 ms <1 ms <1 ms router [192.168.1.254]
2 * * * Request timed out.
3 48 ms 48 ms 81 ms 41.181.53.213
4 43 ms 41 ms 43 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
5 94 ms 40 ms 41 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
6 48 ms 50 ms 74 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 69 ms 70 ms 69 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
8 65 ms 64 ms 64 ms jh-cr-2.za--jh-cr-1.za-a.mtnns.net [196.44.31.255]
9 62 ms 62 ms 63 ms 196.44.31.99
10 69 ms 68 ms 67 ms 196.30.1.53
11 64 ms 62 ms 64 ms 196.31.220.25
12 68 ms 68 ms 68 ms 196.31.63.206
13 61 ms 63 ms 63 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
14 68 ms 68 ms 69 ms 197.242.144.102

Trace complete.


Then to top it off...

On Afrihosts's Auto assigned DNS servers:

C:\>tracert google.com
Unable to resolve target system name google.com.

C:\>nslookup google.com
Server: router
Address: 192.168.1.254

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to router timed-out

So I change it tot Google's DNS servers:

C:\>nslookup google.com
Server: router
Address: 192.168.1.254

Non-authoritative answer:
Name: google.com
Addresses: 2c0f:fb50:4002:803::200e
216.58.223.46


C:\>tracert google.com

Tracing route to google.com [216.58.223.46]
over a maximum of 30 hops:

1 <1 ms * <1 ms router [192.168.1.254]
2 * * * Request timed out.
3 36 ms 38 ms 38 ms 41.181.51.181
4 71 ms 36 ms 42 ms 41.181.51.182
5 37 ms 34 ms 38 ms tb-dca-2.za--qux-i.za.mtnbusiness.net [66.8.11.186]
6 84 ms 73 ms 64 ms compj-cpt-1.mtnns.net [196.44.18.2]
7 178 ms 220 ms 178 ms ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]
8 184 ms 184 ms 183 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.187]
9 185 ms 190 ms 186 ms google-peering-ls-pr-2.uk.mtnns.net [209.212.99.13]
10 177 ms 177 ms 177 ms 209.85.255.76
11 202 ms 201 ms 202 ms 66.249.95.9
12 203 ms 202 ms 202 ms 72.14.239.129
13 199 ms 195 ms 194 ms jnb01s08-in-f14.1e100.net [216.58.223.46]

Trace complete.


Now my two questions;

1. Why are all the traceroutes' 3rd and 4th hops different everytime?
2. Why would your DNS servers not resolve properly? (even in the last hop of the traceroutes!)
 
AfriGenie said:
The issue that started on Friday evening specifically only started on Friday evening, if you experienced any latency or packet loss before then we'll need to look into this as an individual case.

Are you seeing packet loss in general or only during specific times? To which sites or services are you noticing this?
Click to expand...
i'm not sure on the times as they come and go at random,anything from 1% up to 10%,i see it on my Teamspeak.
 
djbrendan said:
i'm not sure on the times as they come and go at random,anything from 1% up to 10%,i see it on my Teamspeak.
Click to expand...

Is there a specific Teamspeak server that this keeps happening on? Or are you noticing it happen across a number of servers? When you notice the packet loss, do any other services tank out as well?
 
AfriGenie said:
Is there a specific Teamspeak server that this keeps happening on? Or are you noticing it happen across a number of servers? When you notice the packet loss, do any other services tank out as well?
Click to expand...

i only use 3 and see packet loss on these servers,i will try others tonight and see if its server specific
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X