Afrihost Business Uncapped Feedback - 2

Status
Not open for further replies.
ghostR said:
Hi Rhodad,

ICMP requests have been turned off at the exchange.

In order to test for exchange congestion (or IPC Congestion by comparing this to the 3rd hop on your traceroute) - Please go to command prompt and ping 155.239.255.250 - Post the results here along with a traceroute, and we'll be able to see where the problem lies.
Click to expand...

Not sure if that's a valid way to determine congestion though. Usually the most straightforward way to determine congestion is to see if high latency is seen across the board.
 
AfriGuy said:
Not sure if that's a valid way to determine congestion though. Usually the most straightforward way to determine congestion is to see if high latency is seen across the board.
Click to expand...

Nope, That IP is the gateway IP of the BRAS/BNG (only works on lines whereby ICMP is disabled on the 2nd hop), So it tests everything from router faults, line faults and exchange faults.
 
ghostR said:
Nope, That IP is the gateway IP of the BRAS/BNG (only works on lines whereby ICMP is disabled on the 2nd hop), So it tests everything from router faults, line faults and exchange faults.
Click to expand...

Whose BRAS though?
 
AfriGuy said:
An ESR is your Edge Service Router in the area, it's a part of the exchange setup.
Telkom are upgrading these routers to Alcatel (I think) hardware which are setup to not response to ICMP requests. Previous to this, timeouts were a bad thing, but it's quite common now and doesn't necessarily reflect an issue.

I'll ask AfriGenie to follow things up if he's had the fault logged :)
Click to expand...

I already said that AH has logged a fault and according to Telkom, it's been resolved.
My question is, now that Telkom has rectified the issue on their side, I am seeing an improvement but it's still not where it's supposed to be, is this because of the issues that AH has been experiencing?
 
AfriGuy said:
An ESR is your Edge Service Router in the area, it's a part of the exchange setup.
Telkom are upgrading these routers to Alcatel (I think) hardware which are setup to not response to ICMP requests. Previous to this, timeouts were a bad thing, but it's quite common now and doesn't necessarily reflect an issue.

I'll ask AfriGenie to follow things up if he's had the fault logged :)
Click to expand...

How do I know if my line is on this new 2nd-hop-timing-out-doesnt-matter kind of router?
 
rhodad said:
I already said that AH has logged a fault and according to Telkom, it's been resolved.
My question is, now that Telkom has rectified the issue on their side, I am seeing an improvement but it's still not where it's supposed to be, is this because of the issues that AH has been experiencing?
Click to expand...

Drop me a PM with your line number and I can double check what's happening here :)
 
rhodad said:
How do I know if my line is on this new 2nd-hop-timing-out-doesnt-matter kind of router?
Click to expand...

You'll know by running a traceroute, it should look something like this:

Code: 
traceroute to mybroadband.co.za (197.242.89.170), 64 hops max, 52 byte packets
 1  router.asus.com (192.168.1.1)  0.974 ms  1.512 ms  0.817 ms
 2  * * *
 3  41.181.53.149 (41.181.53.149)  83.260 ms  58.297 ms  64.459 ms
 4  ipc-recieve-tb-1a.mtnbusiness.net (41.181.53.150)  30.136 ms  57.032 ms  67.145 ms
 5  tb-dca-2.za--qux-c.za.mtnbusiness.net (41.181.198.188)  67.584 ms  35.846 ms  63.981 ms
 6  compj-cpt-1.mtnns.net (196.44.18.2)  19.991 ms
    unc-cpt-1.mtnns.net (196.44.18.8)  39.284 ms
    compj-cpt-1.mtnns.net (196.44.18.2)  20.723 ms
 7  ct-cr-2.za--tb-cr-1.za.mtnns.net (196.44.31.134)  37.128 ms
    196.44.31.106 (196.44.31.106)  35.013 ms  48.677 ms
 8  196.44.0.74 (196.44.0.74)  51.634 ms
    nl-ha-2.za--rb-cr-1.za-a.mtnns.net (196.44.0.121)  40.859 ms  20.221 ms
 9  africainx.cinx.net.za (196.223.22.47)  53.671 ms  27.508 ms  33.065 ms
10  core.gp-cn-het-mee-1.to.gp-hv-ict-mee-1.dfa.p2p.10g.za (41.84.13.66)  61.098 ms  45.383 ms  41.759 ms
11  41-66-132-246-f6.het001-cpe-1-to-gp-cn-het-mee-1.africainx.net (41.66.132.246)  64.124 ms  57.017 ms  53.210 ms
12  core-access-switch1.jnb1.host-h.net (197.189.193.1)  41.721 ms  51.509 ms  46.369 ms
13  row-access-switch1-row3-4.jnb1.host-h.net (197.189.193.36)  51.767 ms  44.375 ms  46.291 ms
14  197.242.89.170 (197.242.89.170)  66.737 ms  58.324 ms  61.242 ms

If you're on an older ESR there will be an IP/ host displayed on the 2nd hop.
PM though, I'll be able to pull up your account info and see what's happening with the fault.
 
AfriGuy said:
You'll know by running a traceroute, it should look something like this:

Code: 
traceroute to mybroadband.co.za (197.242.89.170), 64 hops max, 52 byte packets
 1  router.asus.com (192.168.1.1)  0.974 ms  1.512 ms  0.817 ms
 2  * * *
 3  41.181.53.149 (41.181.53.149)  83.260 ms  58.297 ms  64.459 ms
 4  ipc-recieve-tb-1a.mtnbusiness.net (41.181.53.150)  30.136 ms  57.032 ms  67.145 ms
 5  tb-dca-2.za--qux-c.za.mtnbusiness.net (41.181.198.188)  67.584 ms  35.846 ms  63.981 ms
 6  compj-cpt-1.mtnns.net (196.44.18.2)  19.991 ms
    unc-cpt-1.mtnns.net (196.44.18.8)  39.284 ms
    compj-cpt-1.mtnns.net (196.44.18.2)  20.723 ms
 7  ct-cr-2.za--tb-cr-1.za.mtnns.net (196.44.31.134)  37.128 ms
    196.44.31.106 (196.44.31.106)  35.013 ms  48.677 ms
 8  196.44.0.74 (196.44.0.74)  51.634 ms
    nl-ha-2.za--rb-cr-1.za-a.mtnns.net (196.44.0.121)  40.859 ms  20.221 ms
 9  africainx.cinx.net.za (196.223.22.47)  53.671 ms  27.508 ms  33.065 ms
10  core.gp-cn-het-mee-1.to.gp-hv-ict-mee-1.dfa.p2p.10g.za (41.84.13.66)  61.098 ms  45.383 ms  41.759 ms
11  41-66-132-246-f6.het001-cpe-1-to-gp-cn-het-mee-1.africainx.net (41.66.132.246)  64.124 ms  57.017 ms  53.210 ms
12  core-access-switch1.jnb1.host-h.net (197.189.193.1)  41.721 ms  51.509 ms  46.369 ms
13  row-access-switch1-row3-4.jnb1.host-h.net (197.189.193.36)  51.767 ms  44.375 ms  46.291 ms
14  197.242.89.170 (197.242.89.170)  66.737 ms  58.324 ms  61.242 ms

If you're on an older ESR there will be an IP/ host displayed on the 2nd hop.
PM though, I'll be able to pull up your account info and see what's happening with the fault.
Click to expand...

There is no IP/host on my second hop, just goes:
* * * Request Timed Out
 
Afripeople, could the star citizen download issue be looked into?

It is quite frustrating that an unshaped line can't download at a reasonable rate! The download is over http, not sure what the address is.

The speed is also better during the evenings, if that helps any.
 
Mike43110 said:
Afripeople, could the star citizen download issue be looked into?

It is quite frustrating that an unshaped line can't download at a reasonable rate! The download is over http, not sure what the address is.

The speed is also better during the evenings, if that helps any.
Click to expand...

I'm sure we can get this checked out.
Drop our team a line with details on how to replicate any potential issues and we can take it from there :)
 
AfriGuy said:
Check your inbox :) Just replied with a little more info around the fault.
Click to expand...

Thanks
Just replied

My concern, well one of my concerns is that if I am in fact running on one of these 2nd-hop-timing-out-doesnt-matter kind of routers, when I next need to contact AH support, they'll tell me it's a Telkom issue because my trace route reflects a timeout on the 2nd hop.
Is everyone in the AH support department aware of these special routers and are they aware that a 2nd hop timeout means nothing in these cases?
 
Dianysis said:
No load shedding in my area, but since 19:30, my speed is the best it has been in weeks - sitting at nearly 350 kB/s for p2p on 4mbps line. Coincidence considering all the load shedding happening at the moment?
Click to expand...

Well that was short lived. Everything dog slow - browsing, YouTube streaming, p2p, http download. :(
 
rhodad said:
Thanks
Just replied

My concern, well one of my concerns is that if I am in fact running on one of these 2nd-hop-timing-out-doesnt-matter kind of routers, when I next need to contact AH support, they'll tell me it's a Telkom issue because my trace route reflects a timeout on the 2nd hop.
Is everyone in the AH support department aware of these special routers and are they aware that a 2nd hop timeout means nothing in these cases?
Click to expand...

Our teams know about the changes, yes. Let's continue to chat via DM though :)
 
Beautiful:

AH:

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

1 2 ms 1 ms 2 ms 192.168.0.1
2 35 ms 34 ms 39 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.
1]
3 26 ms 28 ms 28 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178
.77]
4 41 ms 41 ms 39 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 * 41 ms 35 ms jh-cr-2.za--rb-cr-1.za-b.mtnns.net [196.44.31.17
1]
6 40 ms * 79 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 29 ms 29 ms 28 ms 196.44.31.99
8 42 ms 40 ms 34 ms 196.31.220.8
9 * 45 ms * 196.31.220.27
10 62 ms * 80 ms 196.31.63.202
11 78 ms 50 ms 90 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
12 38 ms 43 ms 32 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

WA:

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.0.1
2 29 ms 37 ms * 196-210-149-129.dynamic.isadsl.co.za [196.210.14
9.129]
3 27 ms * 25 ms 196.38.73.113
4 37 ms 39 ms 29 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 30 ms 33 ms * core2b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.63]

6 26 ms 26 ms 38 ms 196.26.0.130
7 35 ms 49 ms 47 ms 41-208-29-126.mtnns.net [41.208.29.126]
8 * 43 ms 36 ms jh-cr-2.za--jh-pr-1.za.mtnns.net [196.44.0.223]

9 29 ms 33 ms 29 ms 196.44.31.99
10 29 ms * 34 ms 196.30.1.53
11 29 ms 36 ms 28 ms 196.31.220.27
12 29 ms * 45 ms 196.31.63.202
13 36 ms 41 ms 39 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
14 * 30 ms 42 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.
 
Dianysis said:
Beautiful:

AH:

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

1 2 ms 1 ms 2 ms 192.168.0.1
2 35 ms 34 ms 39 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.
1]
3 26 ms 28 ms 28 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178
.77]
4 41 ms 41 ms 39 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 * 41 ms 35 ms jh-cr-2.za--rb-cr-1.za-b.mtnns.net [196.44.31.17
1]
6 40 ms * 79 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 29 ms 29 ms 28 ms 196.44.31.99
8 42 ms 40 ms 34 ms 196.31.220.8
9 * 45 ms * 196.31.220.27
10 62 ms * 80 ms 196.31.63.202
11 78 ms 50 ms 90 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
12 38 ms 43 ms 32 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

WA:

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.0.1
2 29 ms 37 ms * 196-210-149-129.dynamic.isadsl.co.za [196.210.14
9.129]
3 27 ms * 25 ms 196.38.73.113
4 37 ms 39 ms 29 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 30 ms 33 ms * core2b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.63]

6 26 ms 26 ms 38 ms 196.26.0.130
7 35 ms 49 ms 47 ms 41-208-29-126.mtnns.net [41.208.29.126]
8 * 43 ms 36 ms jh-cr-2.za--jh-pr-1.za.mtnns.net [196.44.0.223]

9 29 ms 33 ms 29 ms 196.44.31.99
10 29 ms * 34 ms 196.30.1.53
11 29 ms 36 ms 28 ms 196.31.220.27
12 29 ms * 45 ms 196.31.63.202
13 36 ms 41 ms 39 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
14 * 30 ms 42 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.
Click to expand...

Can't tell much from these, they look quite similar. What's your experience like using the other account?
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X