I've found the source of the problem at our side. We are now propagating
IGP table + BGP peers table to your network instead of propagating of
195.16.96/19 + 62.64/19 + M9-PEERS. The problem will be fixed in 24 hours.
Recomended solution for your side now is to accept the default route
recieved from our side and accept all networks with ASPATH ^8263 ?$ and
decline accepting of ^8263$. We are now working on this problem - it seems
to be incorrect working of our BGP routing server.
Thanks for assistance,
Victor L. Belov @ Teleport-TP NOC
+7 095 234 7000 Ext #13
"inet-admins" Internet access mailing list. Maintained by East Connection ISP.
Mail "unsubscribe inet-admins" to Majordomo@east.ru if you want to quit.
List archive is accessible at http://www.east.ru/inet-admins/