from europe, serbia seems to be working via level3... # traceroute 66.185.0.198 traceroute to 66.185.0.198 (66.185.0.198), 30 hops max, 40 byte packets 1 XX.verat.net (213.244.xx.xxx) 0.780 ms 1.692 ms 1.697 ms 2 XX.verat.net (217.26.xx.xxx) 3.062 ms 3.054 ms 3.018 ms 3 clint.noc.verat.net (62.108.96.77) 2.973 ms 2.938 ms 2.901 ms 4 195.178.34.125 (195.178.34.125) 2.839 ms 3.000 ms 2.968 ms 5 212.200.5.105 (212.200.5.105) 15.477 ms 15.383 ms 15.333 ms 6 212.73.203.245 (212.73.203.245) 15.400 ms 14.308 ms 14.914 ms 7 ae-0-11.bar1.vienna1.level3.net (4.69.153.149) 14.730 ms 14.615 ms 14.648 ms 8 ae-12-12.ebr2.frankfurt1.level3.net (4.69.153.146) 158.533 ms 158.503 ms 158.468 ms 9 ae-93-93.csw4.frankfurt1.level3.net (4.69.163.14) 159.090 ms ae-83-83.csw3.frankfurt1.level3.net (4.69.163.10) 158.330 ms 158.264 ms 10 ae-81-81.ebr1.frankfurt1.level3.net (4.69.140.9) 158.135 ms ae-71-71.ebr1.frankfurt1.level3.net (4.69.140.5) 158.150 ms ae-91-91.ebr1.frankfurt1.level3.net (4.69.140.13) 155.613 ms 11 ae-47-47.ebr2.paris1.level3.net (4.69.143.142) 158.885 ms * 158.402 ms 12 ae-41-41.ebr2.washington1.level3.net (4.69.137.50) 156.600 ms ae-44-44.ebr2.washington1.level3.net (4.69.137.62) 154.621 ms 157.051 ms 13 ae-72-72.csw2.washington1.level3.net (4.69.134.150) 156.779 ms ae-92-92.csw4.washington1.level3.net (4.69.134.158) 158.681 ms ae-72-72.csw2.washington1.level3.net (4.69.134.150) 164.913 ms 14 ae-81-81.ebr1.washington1.level3.net (4.69.134.137) 154.991 ms ae-91-91.ebr1.washington1.level3.net (4.69.134.141) 155.272 ms 156.546 ms 15 ae-2-2.ebr3.atlanta2.level3.net (4.69.132.85) 158.204 ms 158.965 ms 158.492 ms 16 ae-7-7.ebr3.dallas1.level3.net (4.69.134.21) 157.186 ms 157.565 ms 157.564 ms 17 ae-93-93.csw4.dallas1.level3.net (4.69.151.169) 159.837 ms ae-83-83.csw3.dallas1.level3.net (4.69.151.157) 158.034 ms ae-73-73.csw2.dallas1.level3.net (4.69.151.145) 156.320 ms 18 ae-82-82.ebr2.dallas1.level3.net (4.69.151.154) 161.284 ms ae-72-72.ebr2.dallas1.level3.net (4.69.151.142) 158.624 ms 159.402 ms 19 ae-5-5.car1.kansascity1.level3.net (4.69.135.229) 156.168 ms 156.481 ms 158.202 ms 20 ae-11-11.car2.kansascity1.level3.net (4.69.135.234) 160.914 ms 158.152 ms 160.836 ms 21 iowa-networ.car2.kansascity1.level3.net (4.53.34.114) 180.620 ms 180.514 ms 180.249 ms 22 ins-db1-et-12-1.desm.netins.net (167.142.67.6) 180.053 ms 179.767 ms 179.712 ms 23 prairieinet.desm.netins.net (167.142.53.18) 179.123 ms 178.434 ms 178.410 ms 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *
host is btw. pingable: # ping 66.185.0.198 -A -q -c 5 PING 66.185.0.198 (66.185.0.198) 56(84) bytes of data. --- 66.185.0.198 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 657ms rtt min/avg/max/mdev = 162.617/163.933/165.772/1.296 ms, ipg/ewma 164.282/163.237 ms generally, it's visible from routers in Germany, and West Coast... On Fri, Aug 2, 2013 at 7:07 AM, Kenny Kant <akennyk...@gmail.com> wrote: > Gang, > > I apologize for a double post on this same topic tonight however I thought > that broadening my request may help our cause. This month we had one of > our IP allocations revoked and just recently got everything squared away > with ARIN and things are "turned back" on so to speak. > > However I still have some customers having issues hitting a number of > financial related websites ..etc and I assume its because of bogons ..etc > > I saw some earlier posts on here where folks have posted their allocation > to ensure that others are routing it properly so I wanted to do the same. > > My allocation which has recently been revived: 66.185.0.0/20 > > Test point traceroute .etc 66.185.0.198 > > We do seem to be having some issues with some level 3 routing our range to > some desitnations and can provide specifics off list. > > Thanks all for the help / verification. > > Kenny > -- ricky
