BGP path selection

Hello!

I try to find out, why shorter AS path is not used.
We have CCR1016-12G, with 6.0rc11.
peer options:

     tcp-md5-key="" nexthop-choice=default multihop=no route-reflect=no hold-time=3m 
     ttl=default in-filter="" out-filter=as-elkdata-out address-families=ip,ipv6 
     default-originate=never remove-private-as=no as-override=no passive=no use-bfd=no

instance options:

      redistribute-connected=no 
      redistribute-static=no redistribute-rip=no redistribute-ospf=no 
      redistribute-other-bgp=no out-filter=as-elkdata-out client-to-client-reflection=no 
      ignore-as-path-len=no routing-table=""

Any suggestions?

You need to show the routes you have a problem with

do

/ip route print detail where dst-address in x.x.x.x/x

I censored output little bit, hopefully this is not problem. There is lots longer prefixes, they all are only announced by 3327

> ip route print detail where dst-address in 212.47.192.0/19  
Flags: X - disabled, A - active, D - dynamic, 
C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, 
B - blackhole, U - unreachable, P - prohibit 
343 ADb  dst-address=212.47.192.0/19 gateway=88.196.97.X 
        gateway-status=88.196.97.X reachable via  ether11 distance=20 scope=40 
        target-scope=10 bgp-as-path="3249,3327" bgp-origin=igp 
        bgp-communities=3249:10233,3249:11000,3249:11002 received-from=Elion-1 

348  Db  dst-address=212.47.192.0/19 gateway=212.47.215.Y 
        gateway-status=212.47.215.Y reachable via  ether10 distance=20 scope=40 
        target-scope=10 bgp-as-path="3327" bgp-origin=igp received-from=Linx-1

Does both peers use the same BGP instance?

No. I can see where it goes. So, only way to get best AS path is by using same instance? Any workarounds for this?