Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=58 time=44 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=43 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=58 time=43 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=58 time=46 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=43 ms


ping 8.8.8.8

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


Trace Test:

traceroute -n 197.242.144.102

1 10.0.0.2 2 ms
2 Request timed out *
3 41.181.178.3 55 ms
4 41.181.178.2 44 ms
5 41.181.165.1 49 ms
6 196.31.180.4 48 ms
7 196.44.31.9 51 ms
8 196.31.220.8 51 ms
9 196.31.220.2 51 ms
10 196.31.63.2 51 ms
11 197.242.144.1 45 ms


traceroute -n 8.8.8.8

1 10.0.0.2 2 ms 2 ms 2 ms
2 Request timed out * * *
3 41.181.178.3 50 ms 50 ms 50 ms
4 41.181.178.2 42 ms 44 ms 44 ms
5 41.181.165.1 49 ms 51 ms 49 ms
6 196.31.180.4 49 ms 51 ms 49 ms
7 72.14.194.7 43 ms 41 ms
41.181.139.1 47 ms
8 Request timed out * *
72.14.194.7 41 ms
9 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.147


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
 
As of 07:21 PM


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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 191 ms 200 ms 216 ms 105-236-5-193-esr-lo.mtnbusiness.co.za [105.236.
5.193]
3 248 ms 256 ms 260 ms 41.181.201.94
4 300 ms 287 ms 289 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 329 ms 358 ms 368 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 369 ms 314 ms 283 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

7 333 ms 337 ms 335 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]

8 344 ms 345 ms 367 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.22
1]
9 346 ms 337 ms 338 ms 196.31.220.10
10 409 ms 433 ms 446 ms 196.31.220.21
11 353 ms 335 ms 319 ms 196.31.63.202
12 425 ms 372 ms 366 ms 196.30.42.133
13 442 ms 442 ms 394 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.
 
This has been my life since last thursday, please help . I'm going to cut :sick:

C:\Users\WOOOOOOOOOO>tracert mybroadband.co.za

Tracing route to mybroadband.co.za [197.242.89.170]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms login.router [10.0.0.2]
2 576 ms 598 ms 623 ms 105-236-5-65-esr-lo.mtnbusiness.co.za [105.236.5
.65]
3 488 ms 451 ms 473 ms 41.181.221.254
4 472 ms 428 ms 465 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 535 ms 545 ms 545 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 567 ms 444 ms 352 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

7 374 ms 331 ms 321 ms 196.44.0.74
8 455 ms 443 ms 406 ms africainx.cinx.net.za [196.223.22.47]
9 385 ms 394 ms 428 ms CORE.GP-CN-HET-MEE-1.TO.GP-MR-VOD-MEE-1.DFA.P2P.
10G.za.africainx.net [41.84.12.151]
10 412 ms 382 ms 394 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
11 360 ms 400 ms 473 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
12 570 ms 552 ms 525 ms row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
13 * 521 ms 495 ms mybroadband.co.za [197.242.89.170]

Trace complete.

C:\Users\WOOOOOOOOOO>
 
Calv said:
This has been my life since last thursday, please help . I'm going to cut :sick:

C:\Users\WOOOOOOOOOO>tracert mybroadband.co.za

Tracing route to mybroadband.co.za [197.242.89.170]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms login.router [10.0.0.2]
2 576 ms 598 ms 623 ms 105-236-5-65-esr-lo.mtnbusiness.co.za [105.236.5
.65]
3 488 ms 451 ms 473 ms 41.181.221.254
4 472 ms 428 ms 465 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 535 ms 545 ms 545 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 567 ms 444 ms 352 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

7 374 ms 331 ms 321 ms 196.44.0.74
8 455 ms 443 ms 406 ms africainx.cinx.net.za [196.223.22.47]
9 385 ms 394 ms 428 ms CORE.GP-CN-HET-MEE-1.TO.GP-MR-VOD-MEE-1.DFA.P2P.
10G.za.africainx.net [41.84.12.151]
10 412 ms 382 ms 394 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
11 360 ms 400 ms 473 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
12 570 ms 552 ms 525 ms row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
13 * 521 ms 495 ms mybroadband.co.za [197.242.89.170]

Trace complete.

C:\Users\WOOOOOOOOOO>
Click to expand...

This seems like it's more likely to be either exchange congestion or a line fault. Looking at the consistently bad latency from the second hop right until the destination hop. Best to test with another network to confirm - but doesn't look like this is a network latency issue :(
 
soulravanger said:
As of 07:21 PM


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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 191 ms 200 ms 216 ms 105-236-5-193-esr-lo.mtnbusiness.co.za [105.236.
5.193]
3 248 ms 256 ms 260 ms 41.181.201.94
4 300 ms 287 ms 289 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 329 ms 358 ms 368 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 369 ms 314 ms 283 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

7 333 ms 337 ms 335 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]

8 344 ms 345 ms 367 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.22
1]
9 346 ms 337 ms 338 ms 196.31.220.10
10 409 ms 433 ms 446 ms 196.31.220.21
11 353 ms 335 ms 319 ms 196.31.63.202
12 425 ms 372 ms 366 ms 196.30.42.133
13 442 ms 442 ms 394 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.
Click to expand...

This looks like congestion or line fault as well. See my reply below :(
 
Beri said:
Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=58 time=44 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=43 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=58 time=43 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=58 time=46 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=43 ms


ping 8.8.8.8

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


Trace Test:

traceroute -n 197.242.144.102

1 10.0.0.2 2 ms
2 Request timed out *
3 41.181.178.3 55 ms
4 41.181.178.2 44 ms
5 41.181.165.1 49 ms
6 196.31.180.4 48 ms
7 196.44.31.9 51 ms
8 196.31.220.8 51 ms
9 196.31.220.2 51 ms
10 196.31.63.2 51 ms
11 197.242.144.1 45 ms


traceroute -n 8.8.8.8

1 10.0.0.2 2 ms 2 ms 2 ms
2 Request timed out * * *
3 41.181.178.3 50 ms 50 ms 50 ms
4 41.181.178.2 42 ms 44 ms 44 ms
5 41.181.165.1 49 ms 51 ms 49 ms
6 196.31.180.4 49 ms 51 ms 49 ms
7 72.14.194.7 43 ms 41 ms
41.181.139.1 47 ms
8 Request timed out * *
72.14.194.7 41 ms
9 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.147


nslookup thishouldfail.afrihost.com

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

This seems to be similar to the issues roadcat had reported. MTN say that they should return to normal once they are finished with maintenance they are currently busy with. I can't see the descriptions on the hops to confirm this. Maybe post the full trace so I can confirm - but seems to be the same issue :(
 
@Afriman, here ya go:

tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 192.168.1.1
2 7 ms 7 ms 7 ms 105-236-11-193-esr-lo.mtnbusiness.co.za [105.236.11.193]
3 44 ms 12 ms 13 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178.65]
4 13 ms 13 ms 14 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 14 ms 13 ms 12 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 52 ms 51 ms 12 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 18 ms 12 ms 13 ms 72.14.194.74
8 192 ms 191 ms 191 ms 66.249.95.8
9 196 ms 195 ms 195 ms 209.85.253.196
10 201 ms 199 ms 198 ms 72.14.238.16
11 182 ms 191 ms 181 ms google-public-dns-a.google.com [8.8.8.8]


tracert 197.242.144.102

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

1 2 ms 2 ms 2 ms 192.168.1.1
2 8 ms 7 ms 7 ms 105-236-11-193-esr-lo.mtnbusiness.co.za [105.236.11.193]
3 51 ms 14 ms 13 ms ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178.89]
4 14 ms 13 ms 13 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 14 ms 13 ms 13 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 14 ms 14 ms 13 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 14 ms 13 ms 14 ms 196.44.31.99
8 25 ms 12 ms 21 ms 196.30.1.53
9 14 ms 13 ms 16 ms 196.31.220.25
10 14 ms 14 ms 13 ms 196.31.63.206
11 14 ms 22 ms 14 ms 196.30.42.133
12 24 ms 13 ms 13 ms cms-gm.afrihost.com [197.242.144.102]
 
From hop 3 onwards there is a fair bit of jitter. If the peaks of that latency are four times the typical latency, it means that those packets were resent at least twice.
 
Timber_MG said:
From hop 3 onwards there is a fair bit of jitter. If the peaks of that latency are four times the typical latency, it means that those packets were resent at least twice.
Click to expand...

From the 2ms response to the router, I'm guessing these are tests over wireless. Are the also no background services running?

Maybe run an MTR test so we can see whether there is actual packet loss on the line.
 
The tests are to a wireless router in the same room. No other services running and little noise on the channel. I get about 1ms jitter on that 2ms ping which is not substantial in comparison to 40ms jitter elsewhere.

Seeing as lightning is not a risk atm, I'll hook up a fly lead later.
 
AfriMan said:
This seems to be similar to the issues roadcat had reported. MTN say that they should return to normal once they are finished with maintenance they are currently busy with. I can't see the descriptions on the hops to confirm this. Maybe post the full trace so I can confirm - but seems to be the same issue :(
Click to expand...

Thanks
network status show all ok. so that is not correct?
 
Here with a cable:

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 6 ms 6 ms 105-236-11-193-esr-lo.mtnbusiness.co.za [105.236
.11.193]
3 11 ms 10 ms 11 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178
.65]
4 41 ms 49 ms 49 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 12 ms 15 ms 12 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
6 114 ms 11 ms 11 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 13 ms 11 ms 12 ms 72.14.194.74
8 189 ms 190 ms 204 ms 66.249.95.8
9 175 ms 175 ms 175 ms 209.85.244.240
10 207 ms 197 ms 197 ms 72.14.242.166
11 * 202 ms 180 ms 209.85.250.163
12 * * * Request timed out.
13 181 ms 181 ms 181 ms google-public-dns-a.google.com [8.8.8.8]
 
On hops 3 and 4 I get some "*" indicating timeout, surprising that this should happen on ICMP. Care to give us a status update somewhat more transparent than a green light on the web site?
 
Beri said:
Thanks
network status show all ok. so that is not correct?
Click to expand...

It is correct - there is nothing going on that affects general day to day service. It seems like only a few isolated clients experiencing some routing anomalies, but otherwise still getting service. Once the maintenance is complete, we expect those will be resolved. It's really very minor maintenance.
 
Timber_MG said:
On hops 3 and 4 I get some "*" indicating timeout, surprising that this should happen on ICMP. Care to give us a status update somewhat more transparent than a green light on the web site?
Click to expand...

I think we'll have to test what you are experiencing and come up with more definitive results. Not seeing the same when I test from my side so far.
 
Looks like the maintenance is become a little more serious. Have just been informed:

eXWT3Fr.png
 
My account running perfectly tonight. Downloads at full speeds.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X