Afrihost Uncapped ADSL Feedback

Status
Not open for further replies.
There shouldn't be that much more latency as I understand things, except to CT-hosted servers ...? Is there separate international transit from CT and JB?

Ping to EU servers went up from 178ms to +-250ms.

Pinging cpt servers are slower ( 60ms - 70ms ) than pinging jhb servers ( 48 ms ). This is pinging from cpt.
 
This is not an issue for normal internet usage at all. But playing online games internationally or even local for that matter really went down the tubes.

I am sure they will fix it in time, I was just stating the obvious of telling your clients about the problems.
 
Ping to EU servers went up from 178ms to +-250ms.

Pinging cpt servers are slower ( 60ms - 70ms ) than pinging jhb servers ( 48 ms ). This is pinging from cpt.

Yeah CPT servers being slower would make sense - since you're going from CT to JHB IPC via telkom, then back to CT via MTN.
Based on your numbers, I'm guessing latency from CT to JB via MTN is about 15ms, compared to 40ms or so on the telkom backhaul network... so you could expect the international pings to drop 25ms or so once the traffic goes via MTN to joburg?

My pings (jhb) to the europe D3 servers average 200ms.
 
There shouldn't be that much more latency as I understand things, except to CT-hosted servers ...? Is there separate international transit from CT and JB?

Peering at CPT (eg: cinx) will make a huge difference. There are a lot of ISP's that Peer with cinx and therefore it's not _just_ cpt hosted servers, a lot of peering goes direct from CPT to overseas without passing via JHB

eg: on WA

Code:
traceroute to www.hetzner.de (213.133.107.227), 30 hops max, 60 byte packets
 1  192.168.0.1 (192.168.0.1)  0.522 ms  0.420 ms  0.484 ms
 2  wrbs-ip-esr-2.ipnet.wa.co.za (41.185.88.1)  6.504 ms  11.351 ms  13.214 ms
 3  wnls-ipc1-vl-108.wa.co.za (196.220.59.238)  47.169 ms  47.017 ms  46.980 ms
 4  wnls-cr1-vl-801.wa.co.za (41.185.0.67)  44.062 ms  43.822 ms  26.867 ms
 5  41-66-150-41-29.wc-ro-dce-1-to-web001-cpe.africainx.net (41.66.150.41)  46.552 ms  51.809 ms  46.678 ms
 6  core_gb-ld-te-dce-1_to_gb-ld-gs-dce-1_abovenet_p2p__10g.gb (41.84.12.127)  216.502 ms core_gb-ld-te-dce-1_to_gb-ld-gs-dce-1_abovenet_p2p__10g.gb (41.84.12.129)  220.209 ms core_gb-ld-te-dce-1_to_gb-ld-gs-dce-1_abovenet_p2p__10g.gb (41.84.12.127)  214.351 ms
...

That doesnt route via JHB to go international.

Code:
traceroute to www.google.co.za (74.125.233.24), 30 hops max, 60 byte packets
 1  192.168.0.1 (192.168.0.1)  0.589 ms  0.453 ms  0.470 ms
 2  wrbs-ip-esr-2.ipnet.wa.co.za (41.185.88.1)  6.203 ms  10.814 ms  12.938 ms
 3  wnls-ipc1-vl-105.wa.co.za (196.220.59.250)  41.091 ms  41.030 ms  40.927 ms
 4  wnls-cr1-vl-801.wa.co.za (41.185.0.67)  64.985 ms  64.906 ms  64.806 ms
 5  wbrs-csw1-vl-140.wa.co.za (41.185.1.5)  63.681 ms  63.584 ms  63.477 ms
 6  google.cinx.net.za (196.223.22.41)  71.860 ms  70.014 ms  69.891 ms
 7  64.233.174.105 (64.233.174.105)  40.170 ms  66.102 ms  63.452 ms
 8  cpt01s01-in-f24.1e100.net (74.125.233.24)  69.302 ms  38.103 ms  46.037 ms

EG: traceroute to google.com from a server hosted in the Newlands Hetzner datacenter (MTN)

Code:
traceroute to www.google.com (74.125.233.19), 30 hops max, 40 byte packets
 1  41.203.4.89 (41.203.4.89)  0.227 ms *  0.328 ms
 2  196.30.77.74 (196.30.77.74)  1.048 ms  1.109 ms  1.122 ms
 3  196.40.104.65 (196.40.104.65)  1.011 ms  1.059 ms  1.071 ms
 4   (196.7.21.34)  1.196 ms  1.190 ms  1.187 ms
 5  tb-cr-1--ct-cr-1-a.mtnns.net (196.44.31.210)  2.053 ms  2.050 ms  2.047 ms
 6  196.44.0.74 (196.44.0.74)  1.172 ms  2.546 ms  2.510 ms
 7  * 74.125.49.218 (74.125.49.218)  2.562 ms  2.574 ms
 8  64.233.174.105 (64.233.174.105)  2.702 ms  2.716 ms  2.783 ms
 9  cpt01s01-in-f19.1e100.net (74.125.233.19)  2.578 ms  2.634 ms  2.666 ms
...

EG: traceroute to www.amazon.com from server above

Code:
traceroute to www.amazon.com (176.32.98.166), 30 hops max, 40 byte packets
 1  * * *
 2  196.30.77.74 (196.30.77.74)  0.905 ms *  1.024 ms
 3  196.40.104.65 (196.40.104.65)  0.870 ms  0.902 ms *
 4   (196.7.21.34)  0.912 ms  0.926 ms *
 5  tb-nt-1--jp-nt-1-b.mtnns.net (196.44.31.158)  1.895 ms  1.892 ms  1.888 ms
 6  lt-cr-1.uk--tb-cr-2-a.uk.mtn.net (196.44.31.213)  162.220 ms  162.157 ms  162.130 ms
....

traceroute from Afrihosts MTN to amazon.com

Code:
traceroute to www.amazon.com (176.32.98.166), 64 hops max, 52 byte packets
 1  dsl-gw (192.168.1.1)  0.506 ms  0.308 ms  0.310 ms
 2  105-236-9-65-esr-lo.mtnbusiness.co.za (105.236.9.65)  6.999 ms  6.712 ms  6.690 ms
 3  ipc-recieve-rb-4a.za.mtnbusiness.net (41.181.178.89)  66.152 ms  29.563 ms  54.507 ms
 4  rb-cr-1.za--rb-dca-1.za-a.mtnns.net (196.44.0.146)  58.663 ms
    rb-dca-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.120)  68.993 ms  32.402 ms
 5  jh-cr-1.za--rb-cr-2.za.mtnns.net (196.44.0.42)  73.865 ms  33.098 ms  50.991 ms
 6  qux-jh-dca-2.za-b.za.mtnbusiness.net (41.181.165.115)  53.679 ms  31.128 ms  32.209 ms
 7  xe-4-1-0.edge5.amsterdam1.level3.net (212.72.41.89)  222.533 ms  251.050 ms  225.181 ms
...

Bounces around jhb before it even leaves SA.

Obviously the routing via a CPT IPC for MTN adsl will be slightly different to Hetzner but it's the same backbone and clearly they have international routes from CPT - most of the international pipes are located in the Western Cape anyway... I stand corrected, however.
 
Peering at CPT (eg: cinx) will make a huge difference. There are a lot of ISP's that Peer with cinx and therefore it's not _just_ cpt hosted servers, a lot of peering goes direct from CPT to overseas without passing via JHB

eg: on WA

Code:
traceroute to www.hetzner.de (213.133.107.227), 30 hops max, 60 byte packets
 1  192.168.0.1 (192.168.0.1)  0.522 ms  0.420 ms  0.484 ms
 2  wrbs-ip-esr-2.ipnet.wa.co.za (41.185.88.1)  6.504 ms  11.351 ms  13.214 ms
 3  wnls-ipc1-vl-108.wa.co.za (196.220.59.238)  47.169 ms  47.017 ms  46.980 ms
 4  wnls-cr1-vl-801.wa.co.za (41.185.0.67)  44.062 ms  43.822 ms  26.867 ms
 5  41-66-150-41-29.wc-ro-dce-1-to-web001-cpe.africainx.net (41.66.150.41)  46.552 ms  51.809 ms  46.678 ms
 6  core_gb-ld-te-dce-1_to_gb-ld-gs-dce-1_abovenet_p2p__10g.gb (41.84.12.127)  216.502 ms core_gb-ld-te-dce-1_to_gb-ld-gs-dce-1_abovenet_p2p__10g.gb (41.84.12.129)  220.209 ms core_gb-ld-te-dce-1_to_gb-ld-gs-dce-1_abovenet_p2p__10g.gb (41.84.12.127)  214.351 ms
...

That doesnt route via JHB to go international.

Code:
traceroute to www.google.co.za (74.125.233.24), 30 hops max, 60 byte packets
 1  192.168.0.1 (192.168.0.1)  0.589 ms  0.453 ms  0.470 ms
 2  wrbs-ip-esr-2.ipnet.wa.co.za (41.185.88.1)  6.203 ms  10.814 ms  12.938 ms
 3  wnls-ipc1-vl-105.wa.co.za (196.220.59.250)  41.091 ms  41.030 ms  40.927 ms
 4  wnls-cr1-vl-801.wa.co.za (41.185.0.67)  64.985 ms  64.906 ms  64.806 ms
 5  wbrs-csw1-vl-140.wa.co.za (41.185.1.5)  63.681 ms  63.584 ms  63.477 ms
 6  google.cinx.net.za (196.223.22.41)  71.860 ms  70.014 ms  69.891 ms
 7  64.233.174.105 (64.233.174.105)  40.170 ms  66.102 ms  63.452 ms
 8  cpt01s01-in-f24.1e100.net (74.125.233.24)  69.302 ms  38.103 ms  46.037 ms

EG: traceroute to google.com from a server hosted in the Newlands Hetzner datacenter (MTN)

Code:
traceroute to www.google.com (74.125.233.19), 30 hops max, 40 byte packets
 1  41.203.4.89 (41.203.4.89)  0.227 ms *  0.328 ms
 2  196.30.77.74 (196.30.77.74)  1.048 ms  1.109 ms  1.122 ms
 3  196.40.104.65 (196.40.104.65)  1.011 ms  1.059 ms  1.071 ms
 4   (196.7.21.34)  1.196 ms  1.190 ms  1.187 ms
 5  tb-cr-1--ct-cr-1-a.mtnns.net (196.44.31.210)  2.053 ms  2.050 ms  2.047 ms
 6  196.44.0.74 (196.44.0.74)  1.172 ms  2.546 ms  2.510 ms
 7  * 74.125.49.218 (74.125.49.218)  2.562 ms  2.574 ms
 8  64.233.174.105 (64.233.174.105)  2.702 ms  2.716 ms  2.783 ms
 9  cpt01s01-in-f19.1e100.net (74.125.233.19)  2.578 ms  2.634 ms  2.666 ms
...

EG: traceroute to www.amazon.com from server above

Code:
traceroute to www.amazon.com (176.32.98.166), 30 hops max, 40 byte packets
 1  * * *
 2  196.30.77.74 (196.30.77.74)  0.905 ms *  1.024 ms
 3  196.40.104.65 (196.40.104.65)  0.870 ms  0.902 ms *
 4   (196.7.21.34)  0.912 ms  0.926 ms *
 5  tb-nt-1--jp-nt-1-b.mtnns.net (196.44.31.158)  1.895 ms  1.892 ms  1.888 ms
 6  lt-cr-1.uk--tb-cr-2-a.uk.mtn.net (196.44.31.213)  162.220 ms  162.157 ms  162.130 ms
....

traceroute from Afrihosts MTN to amazon.com

Code:
traceroute to www.amazon.com (176.32.98.166), 64 hops max, 52 byte packets
 1  dsl-gw (192.168.1.1)  0.506 ms  0.308 ms  0.310 ms
 2  105-236-9-65-esr-lo.mtnbusiness.co.za (105.236.9.65)  6.999 ms  6.712 ms  6.690 ms
 3  ipc-recieve-rb-4a.za.mtnbusiness.net (41.181.178.89)  66.152 ms  29.563 ms  54.507 ms
 4  rb-cr-1.za--rb-dca-1.za-a.mtnns.net (196.44.0.146)  58.663 ms
    rb-dca-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.120)  68.993 ms  32.402 ms
 5  jh-cr-1.za--rb-cr-2.za.mtnns.net (196.44.0.42)  73.865 ms  33.098 ms  50.991 ms
 6  qux-jh-dca-2.za-b.za.mtnbusiness.net (41.181.165.115)  53.679 ms  31.128 ms  32.209 ms
 7  xe-4-1-0.edge5.amsterdam1.level3.net (212.72.41.89)  222.533 ms  251.050 ms  225.181 ms
...

Bounces around jhb before it even leaves SA.

Obviously the routing via a CPT IPC for MTN adsl will be slightly different to Hetzner but it's the same backbone and clearly they have international routes from CPT - most of the international pipes are located in the Western Cape anyway... I stand corrected, however.

Hmm, I think you're right!
Didn't realise the likes of google were plugged straight into cinx...
 
Whats the chances we will ever see 170MS again pinging EU servers?

Someone was asking me earlier which ISP is best for gaming i was pointing towards Afrihost then i needed to change my mind because since this new MTN network the latency is like 100ms more than what it use to be, so i pointed the person towards mweb sadly.

Any other ISP's still using IS other than MWEB and Openweb? I really can't take this latency anymore, i am using a backup MWEB account more than my Afrihost Uncapped account lately.
 
Last edited:
Whats the chances we will ever see 170MS again pinging EU servers?

Someone was asking me earlier which ISP is best for gaming i was pointing towards Afrihost then i needed to change my mind because since this new MTN network the latency is like 100ms more than what it use to be, so i pointed the person towards mweb sadly.

Any other ISP's still using IS other than MWEB and Openweb? I really can't take this latency anymore, i am using a backup MWEB account more than my Afrihost Uncapped account lately.

MWEB does not use IS, they are their own network.. and for CPT in my experience MWEB > IS
 
hmmmm, i was with MWEB but not again the accounts are cool and all but wow the customer service.. outch.

Indeed it takes like a week to get anything out of email support. MWEB Guy is MWEB's saviour I think though always a quick response from them. If it werent for their prices I'd stick to MWEB.

I am not a gamer so latency is not life and death for me. I do a lot of work remotely so that's where it's important but I can deal with it for now.
 
Indeed it takes like a week to get anything out of email support. MWEB Guy is MWEB's saviour I think though always a quick response from them. If it werent for their prices I'd stick to MWEB.

I am not a gamer so latency is not life and death for me. I do a lot of work remotely so that's where it's important but I can deal with it for now.

Yea the thing that worries me is just we had 170ms before and it was awesome! now we get like 250ms it's like being back in the stone age.

Those who play wow will know above 200 is yellow and below gets green latency, and it was so awesome receiving the green bar :)
 
Yea the thing that worries me is just we had 170ms before and it was awesome! now we get like 250ms it's like being back in the stone age.

Those who play wow will know above 200 is yellow and below gets green latency, and it was so awesome receiving the green bar :)

Indeed.. pings over 200ms internationally (EU) are pretty poor for even SA standards these days.
 
Indeed.. pings over 200ms internationally (EU) are pretty poor for even SA standards these days.

The lowest I've ever seen to EU was 195ms and that was to D3 servers on the MTN network, used to get 205ms on the IS network.

I think once they've sorted out all the routing on the network we'll seem some decent pings.
 
The lowest I've ever seen to EU was 195ms and that was to D3 servers on the MTN network, used to get 205ms on the IS network.

I think once they've sorted out all the routing on the network we'll seem some decent pings.

I can't speak for gaming but I see 160ms pings to googles international servers on MWEB quite frequently.
 
They don't shape on ports, they shape on protocol. So normally P2P would be shaped the most.

I see.. well im quite happy with my p2p speeds so I guess no major point :-) it's not going to help latency
 
Ok well its clear that this move to MTN is not good for gaming. I think I might have to move to someone else.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X