fancy route objects

Dear Gabor, 
 
"Gabor Kiss \(Bitman\)" writes:

>> Dear Colleagues,
>> 
>> Are there these route objects correct (is this some very new feature?)
>> or they come from some software bug?

They are from a software bug, reported to the list in August. The
message which contains instructions on how to fix and prevent this 
is included below. 

>> Three independent user can't get mad the same time.

You underestimate users ;-)

>> Note: these objects cannot be queried. I've browsed the mirrored DB file.
>> 
>> Gabor

Sorry for the inconvenience. We will see to a fix as soon as possible.

Carol Orange
RIPE NCC
 
>> *rt: 127.255.255.255/24
>> *de: TAT GmbH Systeme der grafische Datenverarbeit
>> *or: AS2856
>> *mb: BTNET-MNT
>> *ch: Paul.Dyke at bt.net 970916
>> *so: RIPE
>> 
>> *rt: 127.255.255.255/16
>> *de: upstream provider: Swisscom (formerly Unisource Business Networks)
>> *or: AS3303
>> *mb: CH-UNISOURCE-MNT
>> *ch: bridge at unisource.ch 971017
>> *so: RIPE
>> 
>> *rt: 127.255.255.255/24
>> *de: upstream provider: Swisscom (formerly Unisource Business Networks)
>> *or: AS3303
>> *mb: CH-UNISOURCE-MNT
>> *ch: bridge at unisource.ch 971017
>> *so: RIPE
>> 
>> *rt: 127.255.255.255/23
>> *de: HU-CEU
>> *or: AS2012
>> *mb: AS2012-MNT
>> *ch: gaga at elte.hu 971027
>> *so: RIPE

-----------------------------------------------------------------------