Neotel Routing Issue

Elitehost

Elitehost

Well-Known Member
Joined
Apr 15, 2013
Messages
104
Reaction score
20
Location
South Africa
Hello,

Anyone else using Neotel experiencing local routing issues?

Traceroute from local client to our data centre going via International:

1 <1 ms <1 ms <1 ms 10.254.254.10
2 7 ms 5 ms 3 ms 192.168.200.153
3 28 ms 14 ms 11 ms 192.168.200.145
4 24 ms 29 ms 29 ms 192.168.200.137
5 41 ms 20 ms 16 ms 41.164.9.153
6 15 ms 29 ms 16 ms 41.164.112.3
7 * * * Request timed out.
8 14 ms 17 ms 18 ms 41.164.0.243
9 31 ms 20 ms 17 ms 41.164.0.242
10 18 ms 29 ms 23 ms ix-1-3-0-0.tcore2.KLT-CapeTown.as6453.net[41.206.165.13]
11 136 ms 148 ms 151 ms if-0-0-0.core1.SZ5-Seixal.as6453.net[195.219.129.25]
12 283 ms 174 ms 182 ms if-10-2-1-0.tcore1.SV8-Highbridge.as6453.net[195.219.129.2]
13 171 ms 165 ms 217 ms if-19-2.tcore2.L78-London.as6453.net[80.231.138.22]
14 177 ms 173 ms 196 ms if-15-2.tcore2.LDN-London.as6453.net[80.231.131.118]
15 178 ms 183 ms 174 ms ae4.lon11.ip4.tinet.net [141.136.99.73]
16 186 ms 182 ms 192 ms xe-2-1-2.fra21.ip4.tinet.net[141.136.110.93]
17 187 ms 184 ms 181 ms interoute-gw.ip4.tinet.net [141.136.97.166]
18 248 ms 195 ms 188 ms ae0-0.fra-006-score-1-re1.interoute.net[84.233.207.93]
19 196 ms 185 ms 203 ms ae1-0.ams-koo-score-2-re0.interoute.net[84.233.190.49]
20 200 ms 188 ms 193 ms ae0-0.ams-koo-score-1-re0.interoute.net[84.233.190.1]
21 243 ms 218 ms 217 ms ae1-0.lon-001-score-1-re0.interoute.net[84.233.190.58]
22 190 ms 197 ms 185 ms 89.202.130.234
23 385 ms 364 ms 388 ms 41.74.111.138
24 385 ms 375 ms 370 ms 41.74.111.145
25 382 ms 382 ms 371 ms af2-epico-rtr-01.epiconet.com[196.46.186.35]
26 366 ms 375 ms 370 ms server.avalonisp.co.za [196.46.186.158]

Thanks
 
Interesting:
5 41.160.0.243 (41.160.0.243) 46.303 ms 46.472 ms 46.461 ms
6 41.160.0.242 (41.160.0.242) 46.497 ms 44.651 ms 44.623 ms
7 ix-0-3-0-0.tcore1.JSO-Johannesburg.as6453.net (216.6.55.37) 45.116 ms 45.144 ms 45.133 ms
8 if-2-2.tcore2.JSO-Johannesburg.as6453.net (216.6.55.86) 226.187 ms 225.979 ms 214.350 ms
9 if-0-1-0.core2.PV9-Lisbon.as6453.net (41.206.164.58) 189.169 ms if-0-3-0-0.tcore2.KLT-CapeTown.as6453.net (41.206.165.37) 213.795 ms if-0-1-0.core2.PV9-Lisbon.as6453.net (41.206.164.58) 189.295 ms
10 if-0-0-0.core1.SZ5-Seixal.as6453.net (195.219.129.25) 185.316 ms if-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net (80.231.158.1) 212.874 ms if-0-0-0.core1.SZ5-Seixal.as6453.net (195.219.129.25) 185.228 ms
11 if-10-2-1-0.tcore1.SV8-Highbridge.as6453.net (195.219.129.2) 235.353 ms if-1-3.tcore1.SV8-Highbridge.as6453.net (80.231.158.30) 213.151 ms 213.159 ms
12 if-19-2.tcore2.L78-London.as6453.net (80.231.138.22) 219.247 ms 218.903 ms 213.702 ms
13 if-15-2.tcore2.LDN-London.as6453.net (80.231.131.118) 214.640 ms 223.733 ms 214.741 ms
14 ae4.lon11.ip4.tinet.net (141.136.99.73) 212.909 ms 212.108 ms 214.499 ms
15 xe-0-0-2.fra21.ip4.tinet.net (141.136.110.73) 241.367 ms xe-3-0-2.fra21.ip4.tinet.net (141.136.110.81) 242.834 ms xe-8-1-2.fra21.ip4.tinet.net (141.136.110.101) 241.317 ms
16 interoute-gw.ip4.tinet.net (141.136.97.166) 240.636 ms 239.058 ms 237.267 ms
17 ae0-0.fra-006-score-1-re1.interoute.net (84.233.207.93) 248.584 ms 243.241 ms 244.866 ms
18 ae1-0.ams-koo-score-2-re0.interoute.net (84.233.190.49) 247.266 ms 246.110 ms 246.266 ms
19 ae0-0.ams-koo-score-1-re0.interoute.net (84.233.190.1) 245.757 ms 247.954 ms 248.974 ms
20 ae1-0.lon-001-score-1-re0.interoute.net (84.233.190.58) 275.964 ms 243.149 ms 247.549 ms
21 89.202.130.234 (89.202.130.234) 247.357 ms 244.084 ms 246.702 ms
22 41.74.111.134 (41.74.111.134) 421.602 ms 41.74.111.138 (41.74.111.138) 426.022 ms 41.74.111.134 (41.74.111.134) 424.041 ms
23 41.74.111.145 (41.74.111.145) 424.794 ms 420.984 ms 424.254 ms
24 af2-epico-rtr-01.epiconet.com (196.46.186.35) 424.673 ms 424.630 ms 424.662 ms

Didnt reach the destination in the end, let me try another host.
 
Is it not something to do with the routing of the server host?
Traceroute to mirror.ac.za:
5 41.160.0.243 (41.160.0.243) 46.103 ms 46.294 ms 46.300 ms
6 41.160.0.242 (41.160.0.242) 46.279 ms 44.233 ms 44.773 ms
7 is.jinx.net.za (196.223.14.10) 46.019 ms 45.812 ms 45.975 ms
8 ch11-rba-gi0-2.ip.isnet.net (168.209.1.160) 51.852 ms ch11-rba-gi0-1.ip.isnet.net (196.26.0.30) 47.675 ms ch11-rba-gi0-2.ip.isnet.net (168.209.1.160) 51.540 ms
9 168.209.115.218 (168.209.115.218) 69.673 ms 69.461 ms 69.618 ms
10 jnb2pe1-t81-jnb1pe1-t81.net.tenet.ac.za (155.232.6.78) 70.176 ms 68.412 ms 68.515 ms
11 jhb.mirror.ac.za (155.232.191.200) 69.265 ms 68.724 ms 69.286 ms
 
I'm not in Neotel, but tracing from my local ISP:


3 7 ms 10 ms 9 ms 41-66-151-9-9.ENS001-WIFI-WDSL-OPTEQ-INSIDE.afri
cainx.net [41.66.151.9]
4 11 ms 7 ms 13 ms 41-66-151-10-a.ENS001-WIFI-WDSL-INET0.africainx.
net [41.66.151.10]
5 9 ms 7 ms 7 ms CORE.GP-ID-MEC-1.TO.GP-ID-DCE-2.AINX.P2P.10G.za.
africainx.net [41.84.12.8]
6 7 ms 26 ms 8 ms CORE.GP-CN-R21-MEE-1.TO.GP-ID-MEC-1.DFA.P2P.10G.
za.africainx.net [41.84.12.191]
7 8 ms 8 ms 8 ms CORE.GP-RV-DFA-MEE-1.TO.GP-CN-R21-MEE-1.DFA.P2P.
10G.za.africainx.net [41.84.12.163]
8 9 ms 9 ms 12 ms CORE.GP-MR-MEC-1.TO.GP-RV-DFA-MEE-1.DFA.P2P.10G.
za.africainx.net [41.84.12.188]
9 12 ms 8 ms 9 ms CORE.GP-MR-DCE-1.TO.GP-MR-MEC-1.AINX.P2P.10G.za.
africainx.net [41.84.12.33]
10 9 ms 8 ms 8 ms CORE.GP-MR-MEC-1.TO.GP-MR-NT-MEE-1.AINX.P2P.10G.
za.africainx.net [41.84.12.50]
11 9 ms 8 ms 9 ms amb001-cpe-to-jb-mr-msc-mx.africainx.net [41.66.
132.117]
12 9 ms 10 ms 9 ms 41.74.111.145
13 17 ms 12 ms 12 ms af2-epico-rtr-01.epiconet.com [196.46.186.35]
14 8 ms 10 ms 9 ms server.avalonisp.co.za [196.46.186.158]
 
Similar result from adsl account:
3 26 ms 26 ms 25 ms cdsl1-ctn-vl2376.ip.isnet.net [196.38.72.205]
4 26 ms 26 ms 25 ms 196.35.115.128
5 27 ms 27 ms 26 ms 168.209.2.13
6 23 ms 23 ms 22 ms cp3-ctn-gi0-2.ip.isnet.net [168.209.6.135]
7 26 ms 27 ms 27 ms 168.209.28.70
8 68 ms 59 ms 58 ms mi-za-rba-gsrpe2-gi1-1-2-2689.ip.isnet.net [196.
3.141.105]
9 48 ms 53 ms 48 ms CORE.GP-MR-NT-MEE-1.TO.GP-HV-ECH-F5-MEE-1.DFA.P2
.1G.za.africainx.net [41.84.12.152]
10 48 ms 50 ms 47 ms amb001-cpe-to-jb-mr-msc-mx.africainx.net [41.66.
32.117]
11 48 ms 48 ms 47 ms 41.74.111.145
12 51 ms 51 ms 50 ms af2-epico-rtr-01.epiconet.com [196.46.186.35]
13 46 ms 46 ms 46 ms server.avalonisp.co.za [196.46.186.158]
 
Thanks for the reply, there seems to peering issues from Telkom, Vodacom and Neotel. We have escalated the issue to our network tech and he says all traffic from his side is being routed locally. They are sending traffic towards our servers internationally. If Neotel could comment it would assist in figuring out where this issue lies?

Some ISP's without issues:

Afrihost:

1 <1 ms <1 ms <1 ms Billion.400G [10.0.0.2]
2 10 ms 10 ms 9 ms 105-236-5-1-esr-lo.mtnbusiness.co.za [105.236.5.1]
3 11 ms 11 ms 11 ms 41.181.221.254
4 10 ms 10 ms 10 ms 41.181.198.188
5 58 ms 23 ms 27 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 11 ms 11 ms 11 ms 196.44.31.106
7 12 ms 10 ms 10 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 11 ms 11 ms 12 ms africainx.cinx.net.za [196.223.22.47]
9 57 ms 57 ms 58 ms CORE.GP-MR-MEC-1.TO.GP-MR-NT-MEE-1.AINX.P2P.10G.za.africainx.net [41.84.12.50]
10 34 ms 34 ms 35 ms amb001-cpe-to-jb-mr-msc-mx.africainx.net [41.66.132.117]
11 35 ms 35 ms 34 ms 41.74.111.145
12 37 ms 36 ms 38 ms af2-epico-rtr-01.epiconet.com [196.46.186.35]
13 60 ms 58 ms 59 ms server.avalonisp.co.za [196.46.186.158]


iBurst:

1 4 ms 4 ms 3 ms 10.0.0.2
2 11 ms 10 ms 10 ms iburst-41-213-97-49.iburst.co.za [41.213.97.49]
3 34 ms 35 ms 38 ms 10.90.2.12
4 33 ms 51 ms 35 ms iburst-97-2-196-179.iburst.co.za [196.2.97.179]
5 61 ms 56 ms 55 ms iburst-41-213-1-3.iburst.co.za [41.213.1.3]
6 215 ms 437 ms 325 ms 192.168.0.113
7 34 ms 34 ms 34 ms iburst-41-213-126-26.iburst.co.za [41.213.126.26]
8 35 ms 35 ms 35 ms 196-46-25-168.jb1.napafrica.net [196.46.25.168]
9 37 ms 39 ms 36 ms 41.74.111.161
10 39 ms 54 ms 38 ms 41.74.111.145
11 41 ms 41 ms 40 ms af2-epico-rtr-01.epiconet.com [196.46.186.35]
12 37 ms 36 ms 36 ms server.avalonisp.co.za [196.46.186.158]

XDSL:

1 <1 ms <1 ms <1 ms Billion.400G [10.0.0.2]
2 10 ms 9 ms 9 ms 41.180.5.1.dsl.xdsl.co.za [41.180.5.1]
3 32 ms 32 ms 32 ms 41.221.227.226
4 33 ms 34 ms 33 ms 41.221.226.1
5 35 ms 35 ms 35 ms 41.221.224.1
6 37 ms 32 ms 32 ms 41.221.227.46
7 35 ms 34 ms 33 ms jhb-int-core.001.xdsl.co.za [41.223.60.1]
8 34 ms 32 ms 33 ms 41.138.92.133
9 35 ms 38 ms 37 ms af2-epico-rtr-01.epiconet.com [196.46.186.35]
10 38 ms 33 ms 33 ms server.avalonisp.co.za [196.46.186.158]

IS:

1 1 ms 1 ms 1 ms 192.168.1.1
2 11 ms 11 ms 11 ms 196-210-146-129.dynamic.isadsl.co.za [196.210.146.129]
3 13 ms 13 ms 13 ms cdsl2-ctn-vl2276.ip.isnet.net [196.38.72.125]
4 20 ms 15 ms 15 ms 196.35.115.136
5 13 ms 15 ms 13 ms 168.209.6.12
6 16 ms 16 ms 25 ms cp3-ctn-gi0-1.ip.isnet.net [168.209.2.135]
7 14 ms 19 ms 12 ms 168.209.28.70
8 63 ms 38 ms 36 ms mi-za-rba-gsrpe2-gi1-1-2-2689.ip.isnet.net [196.33.141.105]
9 38 ms 39 ms 38 ms CORE.GP-MR-NT-MEE-1.TO.GP-HV-ECH-F5-MEE-1.DFA.P2P.1G.za.africainx.net [41.84.12.152]
10 39 ms 39 ms 38 ms amb001-cpe-to-jb-mr-msc-mx.africainx.net [41.66.132.117]
11 38 ms 39 ms 42 ms 41.74.111.145
12 43 ms 43 ms 40 ms af2-epico-rtr-01.epiconet.com [196.46.186.35]
13 42 ms 39 ms 39 ms server.avalonisp.co.za [196.46.186.158]

ISP's with peering issues:

Previously mentioned Neotel

Saix Traceroute:

1 tpr-ip-esr-1-fe-1-0-3.telkom-ipnet.co.za (196.25.9.45) 0 msec 0 msec 0 msec
2 lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za (196.43.9.46) 168 msec 168 msec 168 msec
3 te3-7.ccr01.lon09.atlas.cogentco.com (149.6.98.73) 172 msec 168 msec 172 msec
4 te0-7-0-32.ccr22.lon01.atlas.cogentco.com (154.54.36.169) [AS 174] 168 msec
te0-0-0-2.ccr21.lon01.atlas.cogentco.com (154.54.36.165) [AS 174] 172 msec
te0-7-0-32.ccr22.lon01.atlas.cogentco.com (154.54.36.169) [AS 174] 168 msec
5 te2-1.mag02.lon01.atlas.cogentco.com (154.54.74.114) [AS 174] 172 msec 168 msec 168 msec
6 149.6.148.230 [AS 174] 176 msec 176 msec 172 msec
7 41.74.111.138 [AS 37202] [MPLS: Label 304192 Exp 0] 176 msec
41.74.111.134 [AS 37202] [MPLS: Label 304192 Exp 0] 176 msec 176 msec
8 41.74.111.145 [AS 37202] 172 msec 176 msec 176 msec
9 af2-epico-rtr-01.epiconet.com (196.46.186.35) [AS 26422] 176 msec 176 msec 180 msec
10 vz10-pta.za-dns.com (196.46.186.149) [AS 26422] 172 msec 176 msec 176 msec
11 elitehost.co.za (196.46.185.2) [AS 26422] 172 msec 172 msec 176 msectpr-route-server>

Vodacom:
1 192.168.0.1 (192.168.0.1) 0.306 ms 0.302 ms 0.299 ms
2 41.0.42.209 (41.0.42.209) 1.616 ms 1.618 ms 1.614 ms
3 10.117.0.190 (10.117.0.190) 24.408 ms 26.869 ms 32.108 ms
4 10.118.46.42 (10.118.46.42) 179.731 ms 10.118.46.14 (10.118.46.14) 181.983 ms 182.193 ms
5 ae2-76.lon10.ip4.tinet.net (141.136.97.161) 182.974 ms 185.410 ms 187.875 ms
6 xe-2-1-2.fra21.ip4.tinet.net (141.136.110.93) 204.471 ms 170.862 ms xe-7-1-0.fra21.ip4.tinet.net (89.149.183.77) 170.852 ms
7 interoute-gw.ip4.tinet.net (141.136.97.166) 174.114 ms 171.820 ms 171.790 ms
8 ae0-0.fra-006-score-1-re1.interoute.net (84.233.207.93) 177.166 ms 176.420 ms 178.891 ms
9 ae1-0.ams-koo-score-2-re0.interoute.net (84.233.190.49) 181.117 ms 186.918 ms 186.090 ms
10 ae0-0.ams-koo-score-1-re0.interoute.net (84.233.190.1) 190.509 ms 193.201 ms 195.302 ms
11 ae1-0.lon-001-score-1-re0.interoute.net (84.233.190.58) 198.441 ms 209.535 ms 170.385 ms
12 89.202.130.234 (89.202.130.234) 172.158 ms 174.621 ms 173.442 ms
13 41.74.111.138 (41.74.111.138) 353.137 ms 41.74.111.134 (41.74.111.134) 351.482 ms 357.751 ms
14 41.74.111.145 (41.74.111.145) 360.159 ms 364.309 ms 366.042 ms
15 af2-epico-rtr-01.epiconet.com (196.46.186.35) 367.731 ms 372.398 ms 374.474 ms
16 * * *


If Neotel (or others could) provide any insight, it would be greatly appreciated.
 
Response from EPICO Networks

Hi there guys,

Anyone connected to Telkom route internationally to us. Telkom is taking bit of time on updating the as-path filters on their side. Neotel however has not yet agreed to peer with us locally so we route the traffic back over either WACS, Seacom or SAT3.


Elitehost said:
Thanks for the reply, there seems to peering issues from Telkom, Vodacom and Neotel. We have escalated the issue to our network tech and he says all traffic from his side is being routed locally. They are sending traffic towards our servers internationally. If Neotel could comment it would assist in figuring out where this issue lies?

Some ISP's without issues:

Afrihost:

1 <1 ms <1 ms <1 ms Billion.400G [10.0.0.2]
2 10 ms 10 ms 9 ms 105-236-5-1-esr-lo.mtnbusiness.co.za [105.236.5.1]
3 11 ms 11 ms 11 ms 41.181.221.254
4 10 ms 10 ms 10 ms 41.181.198.188
5 58 ms 23 ms 27 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 11 ms 11 ms 11 ms 196.44.31.106
7 12 ms 10 ms 10 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 11 ms 11 ms 12 ms africainx.cinx.net.za [196.223.22.47]
9 57 ms 57 ms 58 ms CORE.GP-MR-MEC-1.TO.GP-MR-NT-MEE-1.AINX.P2P.10G.za.africainx.net [41.84.12.50]
10 34 ms 34 ms 35 ms amb001-cpe-to-jb-mr-msc-mx.africainx.net [41.66.132.117]
11 35 ms 35 ms 34 ms 41.74.111.145
12 37 ms 36 ms 38 ms af2-epico-rtr-01.epiconet.com [196.46.186.35]
13 60 ms 58 ms 59 ms server.avalonisp.co.za [196.46.186.158]


iBurst:

1 4 ms 4 ms 3 ms 10.0.0.2
2 11 ms 10 ms 10 ms iburst-41-213-97-49.iburst.co.za [41.213.97.49]
3 34 ms 35 ms 38 ms 10.90.2.12
4 33 ms 51 ms 35 ms iburst-97-2-196-179.iburst.co.za [196.2.97.179]
5 61 ms 56 ms 55 ms iburst-41-213-1-3.iburst.co.za [41.213.1.3]
6 215 ms 437 ms 325 ms 192.168.0.113
7 34 ms 34 ms 34 ms iburst-41-213-126-26.iburst.co.za [41.213.126.26]
8 35 ms 35 ms 35 ms 196-46-25-168.jb1.napafrica.net [196.46.25.168]
9 37 ms 39 ms 36 ms 41.74.111.161
10 39 ms 54 ms 38 ms 41.74.111.145
11 41 ms 41 ms 40 ms af2-epico-rtr-01.epiconet.com [196.46.186.35]
12 37 ms 36 ms 36 ms server.avalonisp.co.za [196.46.186.158]

XDSL:

1 <1 ms <1 ms <1 ms Billion.400G [10.0.0.2]
2 10 ms 9 ms 9 ms 41.180.5.1.dsl.xdsl.co.za [41.180.5.1]
3 32 ms 32 ms 32 ms 41.221.227.226
4 33 ms 34 ms 33 ms 41.221.226.1
5 35 ms 35 ms 35 ms 41.221.224.1
6 37 ms 32 ms 32 ms 41.221.227.46
7 35 ms 34 ms 33 ms jhb-int-core.001.xdsl.co.za [41.223.60.1]
8 34 ms 32 ms 33 ms 41.138.92.133
9 35 ms 38 ms 37 ms af2-epico-rtr-01.epiconet.com [196.46.186.35]
10 38 ms 33 ms 33 ms server.avalonisp.co.za [196.46.186.158]

IS:

1 1 ms 1 ms 1 ms 192.168.1.1
2 11 ms 11 ms 11 ms 196-210-146-129.dynamic.isadsl.co.za [196.210.146.129]
3 13 ms 13 ms 13 ms cdsl2-ctn-vl2276.ip.isnet.net [196.38.72.125]
4 20 ms 15 ms 15 ms 196.35.115.136
5 13 ms 15 ms 13 ms 168.209.6.12
6 16 ms 16 ms 25 ms cp3-ctn-gi0-1.ip.isnet.net [168.209.2.135]
7 14 ms 19 ms 12 ms 168.209.28.70
8 63 ms 38 ms 36 ms mi-za-rba-gsrpe2-gi1-1-2-2689.ip.isnet.net [196.33.141.105]
9 38 ms 39 ms 38 ms CORE.GP-MR-NT-MEE-1.TO.GP-HV-ECH-F5-MEE-1.DFA.P2P.1G.za.africainx.net [41.84.12.152]
10 39 ms 39 ms 38 ms amb001-cpe-to-jb-mr-msc-mx.africainx.net [41.66.132.117]
11 38 ms 39 ms 42 ms 41.74.111.145
12 43 ms 43 ms 40 ms af2-epico-rtr-01.epiconet.com [196.46.186.35]
13 42 ms 39 ms 39 ms server.avalonisp.co.za [196.46.186.158]

ISP's with peering issues:

Previously mentioned Neotel

Saix Traceroute:

1 tpr-ip-esr-1-fe-1-0-3.telkom-ipnet.co.za (196.25.9.45) 0 msec 0 msec 0 msec
2 lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za (196.43.9.46) 168 msec 168 msec 168 msec
3 te3-7.ccr01.lon09.atlas.cogentco.com (149.6.98.73) 172 msec 168 msec 172 msec
4 te0-7-0-32.ccr22.lon01.atlas.cogentco.com (154.54.36.169) [AS 174] 168 msec
te0-0-0-2.ccr21.lon01.atlas.cogentco.com (154.54.36.165) [AS 174] 172 msec
te0-7-0-32.ccr22.lon01.atlas.cogentco.com (154.54.36.169) [AS 174] 168 msec
5 te2-1.mag02.lon01.atlas.cogentco.com (154.54.74.114) [AS 174] 172 msec 168 msec 168 msec
6 149.6.148.230 [AS 174] 176 msec 176 msec 172 msec
7 41.74.111.138 [AS 37202] [MPLS: Label 304192 Exp 0] 176 msec
41.74.111.134 [AS 37202] [MPLS: Label 304192 Exp 0] 176 msec 176 msec
8 41.74.111.145 [AS 37202] 172 msec 176 msec 176 msec
9 af2-epico-rtr-01.epiconet.com (196.46.186.35) [AS 26422] 176 msec 176 msec 180 msec
10 vz10-pta.za-dns.com (196.46.186.149) [AS 26422] 172 msec 176 msec 176 msec
11 elitehost.co.za (196.46.185.2) [AS 26422] 172 msec 172 msec 176 msectpr-route-server>

Vodacom:
1 192.168.0.1 (192.168.0.1) 0.306 ms 0.302 ms 0.299 ms
2 41.0.42.209 (41.0.42.209) 1.616 ms 1.618 ms 1.614 ms
3 10.117.0.190 (10.117.0.190) 24.408 ms 26.869 ms 32.108 ms
4 10.118.46.42 (10.118.46.42) 179.731 ms 10.118.46.14 (10.118.46.14) 181.983 ms 182.193 ms
5 ae2-76.lon10.ip4.tinet.net (141.136.97.161) 182.974 ms 185.410 ms 187.875 ms
6 xe-2-1-2.fra21.ip4.tinet.net (141.136.110.93) 204.471 ms 170.862 ms xe-7-1-0.fra21.ip4.tinet.net (89.149.183.77) 170.852 ms
7 interoute-gw.ip4.tinet.net (141.136.97.166) 174.114 ms 171.820 ms 171.790 ms
8 ae0-0.fra-006-score-1-re1.interoute.net (84.233.207.93) 177.166 ms 176.420 ms 178.891 ms
9 ae1-0.ams-koo-score-2-re0.interoute.net (84.233.190.49) 181.117 ms 186.918 ms 186.090 ms
10 ae0-0.ams-koo-score-1-re0.interoute.net (84.233.190.1) 190.509 ms 193.201 ms 195.302 ms
11 ae1-0.lon-001-score-1-re0.interoute.net (84.233.190.58) 198.441 ms 209.535 ms 170.385 ms
12 89.202.130.234 (89.202.130.234) 172.158 ms 174.621 ms 173.442 ms
13 41.74.111.138 (41.74.111.138) 353.137 ms 41.74.111.134 (41.74.111.134) 351.482 ms 357.751 ms
14 41.74.111.145 (41.74.111.145) 360.159 ms 364.309 ms 366.042 ms
15 af2-epico-rtr-01.epiconet.com (196.46.186.35) 367.731 ms 372.398 ms 374.474 ms
16 * * *


If Neotel (or others could) provide any insight, it would be greatly appreciated.
Click to expand...
 
Anyone that has services from Africa INX has local peering, but
all others not.
Africa INX have peering links at CINX and JINX so why is the traffic not
routed via local peering.
CINX africainx.cinx.net.za
JINX africainx.jinx.net.za
 
Last edited:
Just an update, local peering issues have been resolved, all Neotel traffic is routing correctly.
 
Hi Kilos,

Its more complicated than that, Africainx don't advertise our routes to anyone we don't want them to advertise it too. Why Telkom was blocking our AS-Path is different story. More "paper work" that was resolved. Neotel, however we broke local routing to them at one stage, and brought up our local peering again. Due to complaints about their users not getting good speedtest results as we are expected to pay for bandwidhth to their network, but they have less content than us, all the traffic is content we serving to their customers. They should pay us to get access to it. :) We did up it again, if their customers get poor results on speedtest due to rate limits and limited access they need to start peering with more local providers. They have very few selected peers. The best way to determine local peering is to actually get an account with ISP in question and test how many of the local providers you get decent speed too. A few of the top ones, may not have good connectivity to the ISP your testing.

Neotel does not publically peer at NapAfrica, along with Telkom, MTN, Vodacom and Internet Solutions. It makes sense to pay for traffic to Telkom, they do have the majority of the broadband users, they clearely ahead of the game and to Internet Solutions. MTN is open to peering but have a few small requirements. Vodacom only peer with SAIX as their upstream it seems? Not sure, looks like no direct link to IS at all. Neotel however do not have the same numbers in volume but do have the a fairly large infrastructure. So it just for a few users that may get upset it makes no sense to give them full capacity to us, many others feel the same way.

458276 international routes on our router.. (not so relevant)
4253 active routes on our router for local networks.

Which of just over 1002 active routes of those local routes is free local peering which anyone in the country that is an ISP can obtain. This is MWEB, Cell-C and a-lot of other provides, VOX Telecom etc. etc.. We effectivly don't pay for traffic to them, and they dont pay for traffic to us. We all take care of our last mile to the peering points ie NapAfrica, JINX etc. Most the voice providers also interconnect and peer for free at NapAfrica , Teraco etc. :) 1/4 the country against Telkom, IS, MTN and Vodacom. They all clearely dictate the market with the right to-do so. However Neotel subscribers access data on our network, not us on theirs. We have Netflow Analyzer for this purpose during the time some of the subscribers were complaining.

Kilos, just please note we have 2 links and 2 nodes at JINX and peering at several other POPs including Teraco NapAfrica. If you referring to why Africainx was not advertising the routes for us, there is more to it. We have our own direct STM-1(s) on Seacom and restoration on other networks including WACS. Its pretty easy for us to send over 300Mbit/s of traffic to them internationally and its cheaper than local transit. We not concernd with a few users on Neotel network. You cant pay a premium service price and guarentee throughput if you do not make all efforts to peer with all relevant parties. Its their NOC that has to explain why they not peering with us, even when we were prepared to carry backhaul straight to them in Midrand with existing fibre. Its political :)

I just noted you replied on another post. I see not even TENET network as per the thread has local peering with NEOTEL then at JINX or CINX considering that I am sure TENET has many subscribers possibly more than some of the bigger guys :) They dont just have a few thousand users. Makes you wonder how many other peers are missing.
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X