Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
ghostR said:
traceroute?
Click to expand...

new


Just thought I should post... 4Mbps ADSL line with Capped account.
 
ghostR said:
some exchanges haven't been moved over yet
Click to expand...

Maybe you can explain to me how the new Telkom DSMS works. Since you seem to be in the "know" as it were.

I've got a few friends with 10Mbps and 4Mbps lines who have had stable lines for months and are now suddenly having their ADSL line profiles synced to well below the speeds they were at. One 10Mbps line is at 4Mbps and another 4Mbps line is at 2Mbps. Telkom seems very keen to charge them for 10Mbps and 4Mbps respectively but they are getting well below that.
 
Last edited:
Centurion03 said:
Maybe you can explain to me how the new Telkom DSMS works. Since you seem to be in the "know" as it were.

I've got a few friends with 10Mbps and 4Mbps lines who have had stable lines for months and are now suddenly having their ADSL line profiles synced to well below the speeds they were at. One 10Mbps line is at 4Mbps and another 4Mbps line is at 2Mbps. Telkom seems very keen to charge them for 10Mbps and 4Mbps respectively but they are getting well below that.
Click to expand...

It's a best effort service. Telkoms cop out.
 
Well whatever the CS:GO issue was is either fixed or it's only in the evenings on week days. Ping/Packet loss has been fine all weekend :)
 
S1ght said:
Well whatever the CS:GO issue was is either fixed or it's only in the evenings on week days. Ping/Packet loss has been fine all weekend :)
Click to expand...

We already established that it's only really bad during peak hours. Network is totally borked. Over it. Month end I'm outta here.

Currently have over 100ms on ts. Same in CS. It's just capacity issues over and over and over again. Seems as though they will never get it right.
 
Masik3R said:
We already established that it's only really bad during peak hours. Network is totally borked. Over it. Month end I'm outta here.

Currently have over 100ms on ts. Same in CS. It's just capacity issues over and over and over again. Seems as though they will never get it right.
Click to expand...

Yea, The network probably won't be as congested over the weekend as it is during the week, No doubt tomorrow 5pm will be the same and latency will be through the roof.
 
Anyone else having quit the increased ping? sitting on 260ms on Teamspeak and Battlefield 170-230ms :/ this increased ping has been running since Friday
 
Tracing route to www.afrihost.co.za [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 221 ms 241 ms 217 ms 41.181.221.253
4 222 ms 219 ms 226 ms 41.181.221.254
5 222 ms 224 ms 229 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
6 229 ms 231 ms 231 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 243 ms 244 ms 241 ms pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66]

8 246 ms 252 ms 274 ms jh-cr-2.za--jh-cr-1.za-a.mtnns.net [196.44.31.25
5]
9 254 ms 253 ms 254 ms 196.44.31.99
10 224 ms 228 ms 235 ms 196.30.1.39
11 263 ms 251 ms 249 ms 196.31.220.21
12 244 ms 242 ms 243 ms 196.31.63.202
13 224 ms 227 ms 230 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
14 271 ms 267 ms 264 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.


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

1 <1 ms 1 ms 1 ms 10.0.0.2
2 * * * Request timed out.
3 241 ms 210 ms 206 ms 41.181.53.213
4 239 ms 232 ms 228 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
5 233 ms 298 ms 234 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
6 213 ms 215 ms 212 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 208 ms 210 ms 206 ms 196.44.31.106
8 232 ms 237 ms 237 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121
]
9 235 ms 232 ms 225 ms africainx.cinx.net.za [196.223.22.47]
10 251 ms 252 ms 248 ms CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za [41.84.13.66]
11 264 ms 258 ms 251 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
12 231 ms 225 ms 227 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
13 247 ms 233 ms 233 ms row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
14 229 ms 220 ms 214 ms 197.242.89.170

Trace complete.
 
djbrendan said:
Tracing route to www.afrihost.co.za [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 221 ms 241 ms 217 ms 41.181.221.253
4 222 ms 219 ms 226 ms 41.181.221.254
5 222 ms 224 ms 229 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
6 229 ms 231 ms 231 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 243 ms 244 ms 241 ms pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66]

8 246 ms 252 ms 274 ms jh-cr-2.za--jh-cr-1.za-a.mtnns.net [196.44.31.25
5]
9 254 ms 253 ms 254 ms 196.44.31.99
10 224 ms 228 ms 235 ms 196.30.1.39
11 263 ms 251 ms 249 ms 196.31.220.21
12 244 ms 242 ms 243 ms 196.31.63.202
13 224 ms 227 ms 230 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
14 271 ms 267 ms 264 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.


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

1 <1 ms 1 ms 1 ms 10.0.0.2
2 * * * Request timed out.
3 241 ms 210 ms 206 ms 41.181.53.213
4 239 ms 232 ms 228 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
5 233 ms 298 ms 234 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
6 213 ms 215 ms 212 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 208 ms 210 ms 206 ms 196.44.31.106
8 232 ms 237 ms 237 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121
]
9 235 ms 232 ms 225 ms africainx.cinx.net.za [196.223.22.47]
10 251 ms 252 ms 248 ms CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za [41.84.13.66]
11 264 ms 258 ms 251 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
12 231 ms 225 ms 227 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
13 247 ms 233 ms 233 ms row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
14 229 ms 220 ms 214 ms 197.242.89.170

Trace complete.
Click to expand...
Try using a webafrica 2 gig free account and run the same tests then post here. Can see if its just a Afrihost problem :)
 
tracert with webafrica , sooooo AH seems to be having a problem again! though i keep getting a timed out 2nd hop???!!!what does that mean

Tracing route to www.afrihost.co.za [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 38 ms 101 ms 100 ms cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194
]
4 37 ms 38 ms 37 ms vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
5 31 ms 31 ms 31 ms 196.35.115.136
6 31 ms 31 ms 31 ms 168.209.2.13
7 38 ms 38 ms 37 ms 168.209.6.131
8 43 ms 31 ms 31 ms mtnns-2.cinx.net.za [196.223.22.31]
9 38 ms 38 ms 38 ms 196.44.0.75
10 49 ms 49 ms 49 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]

11 57 ms 56 ms 56 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.22
1]
12 49 ms 51 ms 49 ms 196.30.1.39
13 59 ms 58 ms 58 ms 196.31.220.21
14 50 ms 51 ms 51 ms 196.31.63.202
15 54 ms 90 ms 54 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
16 48 ms 48 ms 49 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.
 
I think it is easy to replicate the packet loss and latency on Afrihost's network.

So using my free 1GB Afrihost account, I have a monitoring server at home, that specifically tests the IPC links (Cape Town).

A traceroute look like this:
Code: 
[root@dl ~]# traceroute -I 105.237.67.65
traceroute to 105.237.67.65 (105.237.67.65), 30 hops max, 60 byte packets
 1  router.heaven.za.net (10.0.0.1)  1.940 ms  1.911 ms  1.906 ms
 2  * * *
 3  41.181.53.149 (41.181.53.149)  176.918 ms  178.052 ms  179.473 ms
 4  ipc-recieve-tb-1a.mtnbusiness.net (41.181.53.150)  154.864 ms  155.962 ms  157.036 ms
 5  tb-dca-2.za--qux-c.za.mtnbusiness.net (41.181.198.188)  120.128 ms  121.341 ms  123.098 ms
 6  qux--tb-dca-2.za-b.za.mtnbusiness.net (41.181.184.31)  187.657 ms  185.998 ms  187.177 ms
 7  41.181.223.221 (41.181.223.221)  24.211 ms  7.180 ms  7.792 ms
 8  105-237-67-65-esr-lo.mtnbusiness.co.za (105.237.67.65)  131.403 ms  127.567 ms  127.016 m
ps. That latency is not my exchange, it is the IPC links, because the same graphs for other ISPs on my line is perfectly fine. Right now for some reason latency on cape town IPCs for Afrihost.

Either way, to explain what happen above:
I do a traceroute to the IP address assigned to the BRAS or BNG in my case, as I was moved over to an Alcatel router instead of a Cisco one on Telkom's side.
1. DSL router
2. BRAS/BNG not pingable with BNG
3. Afrihost IPC-up-something
4. Afrihost IPC-up-something
5. Afrihost router
6. Afrihost IPC-down-something
7. Afrihost IPC-down-something
8. Afrihost IP address on Telkom BRAS/BNG

How does it work that a packet traverses both direction of the IPC links in a single trace? Easy. Telkom IPC makes use of half-duplex MPLS vpn.

Here are the graphs.
Right now, high latency:

image.jpg


Earlier this week, normal latency high packet loss:

image.jpg


That is some very good information, to pin point exactly where there is packet loss, that the guys notice in CS:GO.
Look no further than IPCs. At least in Cape Town.

EDIT: courtesy of Tinuva
 
Last edited:
nicki said:
GhostR mentioned that some exchanges have been upgraded and the new equipment does not respond to pings.
Click to expand...

aha! i see, but still this indicates that AH has a latency issue again

mweb and Webafrica dont have these insane pings
 
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 8 ms 8 ms 8 ms 105-236-14-193-esr-lo.mtnbusiness.co.za [105.236.14.193]
3 248 ms 255 ms 239 ms 41.181.201.94
4 235 ms 232 ms 228 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 241 ms 248 ms 247 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 226 ms 222 ms 217 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 273 ms 298 ms 256 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]
8 263 ms 271 ms 284 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.221]
9 285 ms 282 ms 276 ms 196.31.220.12
10 223 ms 222 ms 227 ms 196.31.220.25
11 255 ms 260 ms 265 ms 196.31.63.206
12 273 ms 276 ms 265 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
13 270 ms 268 ms 270 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 10 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 9 ms 9 ms 9 ms 165.165.214.213
6 10 ms 10 ms 9 ms 196.43.11.218
7 10 ms 9 ms 9 ms 196.43.25.206
8 60 ms 46 ms 57 ms mtn-gw.telkom-ipnet.co.za [196.25.165.198]
9 32 ms 31 ms 33 ms tb-cr-2.za--tb-pr-1.za-a.mtnns.net [196.44.18.142]
10 31 ms 31 ms 31 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
11 32 ms 31 ms 32 ms jh-cr-2.za--jh-cr-1.za-a.mtnns.net [196.44.31.255]
12 32 ms 31 ms 31 ms 196.44.31.99
13 33 ms 33 ms 34 ms 196.31.220.6
14 33 ms 32 ms 33 ms 196.31.220.23
15 31 ms 31 ms 32 ms 196.31.63.206
16 33 ms 32 ms 33 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
17 31 ms 32 ms 31 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

Can confirm, Afrihost is borked. My Telkom account is A OK.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X