Afrihost CAPPED ADSL Feedback (MTN)

[image132]

Its MTN guys, this has happened before.

They're probably messing with their data centre in Great Westerford after the fire this week.

Even though I still have the issue when I switch to my telkom account?

 

[Shard]

Or afrihost are running at full capacity

I have the same problem on Axxess, so thats MTN Business.

 

[ghostR]

I have the same problem on Axxess, so thats MTN Business.

well, afrihost own axxess so effectively the same capacity really

 

[nicki]

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

1 <1 ms <1 ms <1 ms 192.168.10.1
2 * * * Request timed out.
3 * 35 ms 35 ms 196.38.72.194
4 31 ms 34 ms 33 ms 196.38.72.193
5 * 32 ms 37 ms 196.35.115.136
6 36 ms 34 ms 33 ms 168.209.6.13
7 32 ms 42 ms 34 ms 168.209.6.130
8 * 34 ms 33 ms 41.208.29.210
9 33 ms 34 ms 34 ms 196.44.0.75
10 49 ms 53 ms 51 ms 196.44.31.69
11 51 ms 51 ms 50 ms 196.44.0.221
12 * * 53 ms 196.31.220.12
13 52 ms 50 ms 50 ms 196.31.220.25
14 53 ms 50 ms 50 ms 196.31.63.206
15 53 ms 51 ms 50 ms 196.30.42.133
16 51 ms 50 ms * 197.242.144.102
17 54 ms 52 ms 50 ms 197.242.144.102

Trace complete.

C:\Users\nicki>tracert -d -w 500 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 192.168.10.1
2 * * * Request timed out.
3 * 89 ms 32 ms 196.38.72.194
4 * 132 ms 136 ms 196.38.72.193
5 35 ms 34 ms 34 ms 196.35.115.136
6 135 ms 135 ms * 168.209.6.13
7 * 97 ms 34 ms 168.209.6.130
8 191 ms 38 ms 34 ms 41.208.29.210
9 133 ms * * 196.44.0.75
10 60 ms 51 ms 58 ms 196.44.31.69
11 53 ms 53 ms 51 ms 196.44.0.221
12 54 ms 50 ms 50 ms 196.31.220.12
13 * 51 ms 50 ms 196.31.220.25
14 50 ms 50 ms 50 ms 196.31.63.206
15 54 ms 50 ms 54 ms 196.30.42.133
16 53 ms 50 ms 50 ms 197.242.144.102

Trace complete.

C:\Users\nicki>tracert -d -w 500 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 192.168.10.1
2 * * * Request timed out.
3 * 35 ms 34 ms 196.38.72.194
4 33 ms 34 ms 33 ms 196.38.72.193
5 35 ms 34 ms 33 ms 196.35.115.136
6 36 ms * * 168.209.6.13
7 32 ms 34 ms 36 ms 168.209.6.130
8 32 ms 34 ms 34 ms 41.208.29.210
9 37 ms 32 ms 34 ms 196.44.0.75
10 50 ms 50 ms 50 ms 196.44.31.69
11 51 ms 54 ms * 196.44.31.97
12 52 ms 50 ms 50 ms 196.31.220.12
13 54 ms 50 ms 50 ms 196.31.220.25
14 51 ms 50 ms 50 ms 196.31.63.206
15 51 ms 51 ms * 196.30.42.133
16 53 ms 50 ms 50 ms 197.242.144.102

Trace complete.

 

[ghostR]

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

1 <1 ms <1 ms <1 ms 192.168.10.1
2 * * * Request timed out.
3 * 35 ms 35 ms 196.38.72.194
4 31 ms 34 ms 33 ms 196.38.72.193
5 * 32 ms 37 ms 196.35.115.136
6 36 ms 34 ms 33 ms 168.209.6.13
7 32 ms 42 ms 34 ms 168.209.6.130
8 * 34 ms 33 ms 41.208.29.210
9 33 ms 34 ms 34 ms 196.44.0.75
10 49 ms 53 ms 51 ms 196.44.31.69
11 51 ms 51 ms 50 ms 196.44.0.221
12 * * 53 ms 196.31.220.12
13 52 ms 50 ms 50 ms 196.31.220.25
14 53 ms 50 ms 50 ms 196.31.63.206
15 53 ms 51 ms 50 ms 196.30.42.133
16 51 ms 50 ms * 197.242.144.102
17 54 ms 52 ms 50 ms 197.242.144.102

Trace complete.

C:\Users\nicki>tracert -d -w 500 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 192.168.10.1
2 * * * Request timed out.
3 * 89 ms 32 ms 196.38.72.194
4 * 132 ms 136 ms 196.38.72.193
5 35 ms 34 ms 34 ms 196.35.115.136
6 135 ms 135 ms * 168.209.6.13
7 * 97 ms 34 ms 168.209.6.130
8 191 ms 38 ms 34 ms 41.208.29.210
9 133 ms * * 196.44.0.75
10 60 ms 51 ms 58 ms 196.44.31.69
11 53 ms 53 ms 51 ms 196.44.0.221
12 54 ms 50 ms 50 ms 196.31.220.12
13 * 51 ms 50 ms 196.31.220.25
14 50 ms 50 ms 50 ms 196.31.63.206
15 54 ms 50 ms 54 ms 196.30.42.133
16 53 ms 50 ms 50 ms 197.242.144.102

Trace complete.

C:\Users\nicki>tracert -d -w 500 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 192.168.10.1
2 * * * Request timed out.
3 * 35 ms 34 ms 196.38.72.194
4 33 ms 34 ms 33 ms 196.38.72.193
5 35 ms 34 ms 33 ms 196.35.115.136
6 36 ms * * 168.209.6.13
7 32 ms 34 ms 36 ms 168.209.6.130
8 32 ms 34 ms 34 ms 41.208.29.210
9 37 ms 32 ms 34 ms 196.44.0.75
10 50 ms 50 ms 50 ms 196.44.31.69
11 51 ms 54 ms * 196.44.31.97
12 52 ms 50 ms 50 ms 196.31.220.12
13 54 ms 50 ms 50 ms 196.31.220.25
14 51 ms 50 ms 50 ms 196.31.63.206
15 51 ms 51 ms * 196.30.42.133
16 53 ms 50 ms 50 ms 197.242.144.102

Trace complete.

better, a lot better.

 

[nicki]

Back on AH:

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

1 <1 ms <1 ms <1 ms 192.168.10.1
2 * * * Request timed out.
3 * * 206 ms 41.181.53.213
4 201 ms 195 ms * 41.181.53.214
5 234 ms 227 ms * 41.181.198.188
6 198 ms 200 ms * 196.44.18.2
7 204 ms 209 ms * 196.44.31.134
8 246 ms 245 ms * 196.44.31.69
9 242 ms 223 ms * 196.44.0.221
10 * 232 ms 230 ms 196.31.220.10
11 * * 223 ms 196.31.220.21
12 * 215 ms 218 ms 196.31.63.202
13 * 240 ms 236 ms 196.30.42.133
14 233 ms * 231 ms 197.242.144.102

Trace complete.

C:\Users\nicki>tracert -d -w 500 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 192.168.10.1
2 * * * Request timed out.
3 * 201 ms 254 ms 41.181.53.213
4 209 ms * * 41.181.53.214
5 215 ms 210 ms * 41.181.198.188
6 193 ms 184 ms * 196.44.18.2
7 222 ms 231 ms * 196.44.31.134
8 227 ms 222 ms * 196.44.31.69
9 215 ms 223 ms * 196.44.31.97
10 250 ms * * 196.31.220.10
11 214 ms 207 ms * 196.31.220.21
12 316 ms * 220 ms 196.31.63.202
13 232 ms 209 ms * 196.30.42.133
14 240 ms 228 ms * 197.242.144.102
15 238 ms 239 ms * 197.242.144.102
16 235 ms 240 ms * 197.242.144.102
17 243 ms 240 ms * 197.242.144.102
18 242 ms 236 ms * 197.242.144.102
19 226 ms 222 ms * 197.242.144.102
20 215 ms * 350 ms 197.242.144.102

Trace complete.

 

[nicki]

The AfriGenies have something to answer for...

 

[image132]

Afrihost

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

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 15 ms 17 ms 8 ms 105-236-14-193-esr-lo.mtnbusiness.co.za [105.236.14.193]
3 200 ms 195 ms 201 ms 41.181.201.94
4 156 ms 157 ms 161 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 157 ms 163 ms 163 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 188 ms 184 ms 186 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
7 183 ms 184 ms 182 ms jh-cr-2.za--jh-cr-1.za-a.mtnns.net [196.44.31.255]
8 190 ms 180 ms 172 ms 196.44.31.99
9 203 ms 227 ms 207 ms 196.31.220.6
10 220 ms 224 ms 217 ms 196.31.220.23
11 212 ms 215 ms 203 ms 196.31.63.206
12 202 ms 203 ms 203 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
13 215 ms 215 ms 217 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

Telkom

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

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 8 ms 8 ms 8 ms wbs-ip-bng-1.south.dsl.telkomsa.net [105.224.243.1]
3 11 ms 9 ms 9 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
4 10 ms 9 ms 9 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
5 10 ms 9 ms 9 ms 196.25.190.209
6 10 ms 9 ms 10 ms 196.43.11.218
7 10 ms 10 ms 9 ms 196.43.25.206
8 11 ms 10 ms 11 ms mtn-gw.telkom-ipnet.co.za [196.25.165.198]
9 11 ms 11 ms 10 ms tb-cr-1.za--tb-pr-1.za-a.mtnns.net [196.44.18.140]
10 11 ms 11 ms 11 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
11 30 ms 30 ms 31 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]
12 30 ms 30 ms 32 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.221]
13 33 ms 32 ms 43 ms 196.31.220.10
14 32 ms 32 ms 32 ms 196.31.220.21
15 30 ms 29 ms 30 ms 196.31.63.202
16 32 ms 32 ms 32 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
17 32 ms 32 ms 32 ms cms-gm.afrihost.com [197.242.144.102]

Well I take it back. My Telkom account is working fine now. Earlier it was just as messed up as my AH one.

 

[Shard]

well, afrihost own axxess so effectively the same capacity really

I'm pretty sure I know this, and that's why I am throwing out the advice for you noobs here.

 

[ghostR]

Afrihost

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

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 15 ms 17 ms 8 ms 105-236-14-193-esr-lo.mtnbusiness.co.za [105.236.14.193]
3 200 ms 195 ms 201 ms 41.181.201.94
4 156 ms 157 ms 161 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 157 ms 163 ms 163 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 188 ms 184 ms 186 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
7 183 ms 184 ms 182 ms jh-cr-2.za--jh-cr-1.za-a.mtnns.net [196.44.31.255]
8 190 ms 180 ms 172 ms 196.44.31.99
9 203 ms 227 ms 207 ms 196.31.220.6
10 220 ms 224 ms 217 ms 196.31.220.23
11 212 ms 215 ms 203 ms 196.31.63.206
12 202 ms 203 ms 203 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
13 215 ms 215 ms 217 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

Telkom

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

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 8 ms 8 ms 8 ms wbs-ip-bng-1.south.dsl.telkomsa.net [105.224.243.1]
3 11 ms 9 ms 9 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
4 10 ms 9 ms 9 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
5 10 ms 9 ms 9 ms 196.25.190.209
6 10 ms 9 ms 10 ms 196.43.11.218
7 10 ms 10 ms 9 ms 196.43.25.206
8 11 ms 10 ms 11 ms mtn-gw.telkom-ipnet.co.za [196.25.165.198]
9 11 ms 11 ms 10 ms tb-cr-1.za--tb-pr-1.za-a.mtnns.net [196.44.18.140]
10 11 ms 11 ms 11 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
11 30 ms 30 ms 31 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]
12 30 ms 30 ms 32 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.221]
13 33 ms 32 ms 43 ms 196.31.220.10
14 32 ms 32 ms 32 ms 196.31.220.21
15 30 ms 29 ms 30 ms 196.31.63.202
16 32 ms 32 ms 32 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
17 32 ms 32 ms 32 ms cms-gm.afrihost.com [197.242.144.102]

Well I take it back. My Telkom account is working fine now. Earlier it was just as messed up as my AH one.

From the second hop, Which suggests that it's IPC congestion, Afrihost to blame and not telkom

 

[nicki]

Why do you guys get a response on 2nd hop?

 

[ghostR]

I'm pretty sure I know this, and that's why I am throwing out the advice for you noobs here.

for you noobs here? Come again?

 

[nicki]

Who is 'our'?

 

[ghostR]

Who is 'our'?

Telkom.

 

[nicki]

Ok but your traces have a response on 2nd, mine does not? Is it per exchange?

 

[image132]

From the second hop, Which suggests that it's IPC congestion, Afrihost to blame and not telkom

Agreed. But earlier when telkom was being broken as well on hop 5 actually I didn't know what to think. Just glad I have 1 working account now.

 

[ghostR]

Agreed. But earlier when telkom was being broken as well on hop 5 actually I didn't know what to think. Just glad I have 1 working account now.

Probably a router along the line, If the issue is at hop 2, it is exchange issue, if the issue starts at hop 3 it is ISP issue. If its 4 and onwards it is a problem in the ISP's network

 

[ghostR]

Ok but your traces have a response on 2nd, mine does not? Is it per exchange?

some exchanges haven't been moved over yet

 

[nerevar]

so local 150+ms, int 350+ms, working on IS accounts, great success.

 

[ghostR]

so local 150+ms, int 350+ms, working on IS accounts, great success.

traceroute?