Peering issue or routing issue?

I

irBosOtter

Expert Member
Joined
Feb 14, 2014
Messages
2,933
Reaction score
984
Location
Cape Town
Not really sure what is on this IP of 196.41.99.9, might be one of the akamai servers, but why bother if traffic routes all the way to London and back to CPT lol



c:\>tracert 196.41.99.9

Tracing route to 196.41.99.9 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms [10.1.5.1]
2 2 ms 3 ms 3 ms 10.1.230.1
3 * * * Request timed out.
4 1 ms <1 ms <1 ms *.*.*.*
5 13 ms 11 ms 1 ms *.*.*.*
6 1 ms 1 ms 5 ms ix-0-3-0-0.tcore1.klt-cape-town.as6453.net [41.2
06.164.9]
7 129 ms 126 ms 123 ms if-0-1-1.core2.pv9-lisbon.as6453.net [41.206.164
.65]
8 151 ms 192 ms 150 ms if-0-0-0-2000.tcore1.pv9-lisbon.as6453.net [80.2
31.158.1]
9 149 ms 177 ms 148 ms if-1-3.tcore1.sv8-highbridge.as6453.net [80.231.
158.30]
10 149 ms 149 ms 170 ms if-19-2.tcore2.l78-london.as6453.net [80.231.138
.22]
11 151 ms 152 ms 151 ms if-15-2.tcore2.ldn-london.as6453.net [80.231.131
.118]
12 149 ms 149 ms 149 ms if-4-0-0.core4.ldn-london.as6453.net [80.231.62.
26]
13 153 ms 192 ms 151 ms ix-2-0-6-223.core4.ldn-london.as6453.net [195.21
9.195.226]
14 181 ms 149 ms 148 ms th201-lon-gi-321.borwood.net [217.78.88.146]
15 332 ms 338 ms 405 ms ct201-cpt-po-wacs.borwood.net [217.78.88.202]
16 196 ms 202 ms 225 ms ct102-cpt-gi-2901.borwood.net [217.78.92.149]
17 * * 210 ms 96.172.ct-dc.ctcore.net [196.41.96.172]
18 254 ms 226 ms 222 ms 96.164.ct-dc.ctcore.net [196.41.96.164]
19 243 ms 238 ms 240 ms 196.41.99.9

Trace complete.
 
Most probably a routing issue, BUT you blocked out the most important IPs in the traceroute to really know where it went wrong. Bad habit thinking you are hiding your own IP.
 
Tinuva said:
Most probably a routing issue, BUT you blocked out the most important IPs in the traceroute to really know where it went wrong. Bad habit thinking you are hiding your own IP.
Click to expand...


I'm not thinking I'm hiding our external IP, I am hiding it.
 
This looks better over RSAweb line, so probably a neotel issue then

Tracing route to 196.41.99.9 over a maximum of 30 hops

1 3 ms 5 ms 5 ms 10.1.5.1
2 3 ms 3 ms 3 ms 10.1.230.1
3 <1 ms <1 ms <1 ms 10.1.200.254
4 <1 ms <1 ms <1 ms *.*.*.* - Hiding our public IP!
5 1 ms 1 ms 1 ms *.*.*.* - Hiding as it's on site as well...
6 1 ms 1 ms 1 ms 41.215.238.169
7 2 ms 1 ms 1 ms 196.223.22.39
8 1 ms 1 ms 1 ms 196.41.96.164
9 1 ms 1 ms 1 ms 196.41.99.9

Trace complete.
 
And another one over Telkom ADSL, also going half way around the world...
C:\tracert -d 196.41.99.9

Tracing route to 196.41.99.9 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.15.5.1
2 <1 ms <1 ms <1 ms 10.15.15.254
3 7 ms 7 ms 6 ms 105.224.200.1 - no need to hide any IP's here
4 8 ms 7 ms 8 ms 105.226.0.6
5 8 ms 7 ms 8 ms 105.226.0.13
6 7 ms 7 ms 7 ms 165.165.221.153
7 29 ms 30 ms 30 ms 196.43.51.250
8 134 ms 134 ms 134 ms 116.0.79.45
9 292 ms 276 ms 278 ms 180.87.36.17
10 276 ms 276 ms 278 ms 180.87.37.10
11 274 ms 272 ms 273 ms 80.231.130.5
12 276 ms 276 ms 276 ms 80.231.130.130
13 281 ms 277 ms 277 ms 80.231.76.85
14 224 ms 223 ms 224 ms 195.219.195.226
15 215 ms 214 ms 213 ms 217.78.88.146
16 390 ms 378 ms 376 ms 217.78.88.202
17 214 ms 223 ms 214 ms 217.78.92.149
18 216 ms 219 ms 216 ms 217.78.92.233
19 214 ms 215 ms 214 ms 196.41.96.164
20 * 220 ms 228 ms 196.41.99.9

Trace complete.
 
Probably a tactical move, to make sure other ISP's users don't use their Akamai cluster, or at least ISPs that don't peer with them.

Look at this trace too:
Code: 
traceroute to 196.41.99.9 (196.41.99.9), 30 hops max, 60 byte packets
 1  net-26.cr1.gw.cpt.za.wadns.net (41.185.26.2)  4.215 ms  4.160 ms  4.143 ms
 2  cybersmart.ct1.napafrica.net (196.46.25.58)  4.139 ms  4.120 ms  4.110 ms
 3  196.41.99.9 (196.41.99.9)  4.081 ms  4.069 ms  4.052 ms
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X