If you see inaccuracies in the results, please visit:
https://www.ripe.net/contact-form?topic=ripe_dbm&show_form=true
Source
Objects returned came from source
RIPE
Terms and Conditions
This is the RIPE Database query service. The objects are in RDAP format.
http://www.ripe.net/db/support/db-terms-conditions.pdf
Notice
======Uplinks======
-----------Peering Ltd-----------
-----------TRANSTELECOM-----------
-----------Rostelecom-----------
-----------Fiord-----------
-----------Global-Net-----------
-----------Inetcom-----------
======Downlinks======
-----------LLC "Zummer"-----------
-----------Dancer LLC-----------
-----------Jamal-Kontinent Ltd-----------
-----------Nadym Svyaz Servis-----------
-----------Progress Tehnologiya LLC-----------
-----------Connect LLC-----------
-----------Aileron LLC-----------
-----------Arctel LLC-----------
-----------Yamal-Soft 2003 Ltd.-----------
-----------JSC Pursvyaz-----------
-----------12 bit LLC-----------
-----------Courier Plus Ltd-----------
-----------UTEKTV-----------
-----------CityLink Ltd-----------
-----------N-Telecom Ltd-----------
-----------Ekaterinburg-2000 LLC-----------
-----------Ezerdi LLC-----------
-----------"Russian company" LLC-----------
-----------Andial Ltd.-----------
-----------Metroset Ltd-----------
-----------OKKO LLC-----------
-----------LLC 12BIT-----------
-----------LLC Zero Kilometer-----------
-----------Elektronnyj Yugansk Ltd-----------
----------- LLC IVI.RU -----------
----------- LLC "NZRRTA" -----------
----------- Russian Company Sever LLC-----------
----------- 23Net-----------
======Peers======
-----------JSC Intersvyaz-2-----------
-----------MSK-IX-RS-----------
-----------EKT-IX-RS-----------
-----------INSYS LLC-----------
-----------CJSC Russian company-----------
-----------"Permtelecom" Ltd-----------
-----------Piter-IX-----------
-----------NSK-IX-----------
-----------Google-----------
-----------LLC Cifrovie Seti Urala-----------
-----------Lifestream Ltd-----------
-----------JSC "Ufanet"-----------
====================================================
BGP communities accepted from downstream
1. Common, prepending to all upstreams:
51028:5000X, where
0 < X < 6 - prepend X times 51028 to all upstreams
2. Specific, prepending to upstream NN
51028:60NNX, where:
NN - upstream
00 - Cloud-IX
01 - Fiord
02 - Rostelecom
03 - MSK-IX
04 - Data-IX
05 - Inetcom
06 - GlobalNET
07 - Transtelecom
08 - Piter-IX
X - Action
X = 0 - do not announce
0 < X < 6 - prepend X times 51028
3. Specific, prepending to all peers
51028:6100X, where:
4. Specific, prepending to Google
51028:6110X, where:
5. Blackhole
51028:666, /25-/32 prefixes accepted
For /32 prefixes with community blackhole (51028:666), we add community Blackhole for some of our Uplinks and announce them.
In order not to announce the /32 blackhole Uplink, also use the community on point 2 (51028:60NN0)
*Relevant if you do not announce your networks to specific uplinks
NN - upstream, where:
02 - Rostelecom (add 12389:55555)
05 - Inetcom (add 35598:666)
07 - Transtelecom (add 20485:65535)
All inbound prefixes are marked with BGP communities
which describe which node the announcement was received from
This format is 51028:300NN where the fields are:
NN - number of node:
01 - cr01.msk (Moscow)
02 - cr02.msk (Moscow)
03 - cr01.nnv (N.Novgorod)
04 - cr01.yekt (Yekaterinburg)
05 - cr01.chl (Chelyabinsk)
06 - cr01.tmn (Tyumen)
07 - cr02.tmn (Tyumen)
08 - cr01.nsk (Novosibirsk)
09 - cr01.irk (Irkutsk)
10 - cr01.surg (Surgut)
11 - cr01.nvt (Nijnevartovsk)
12 - cr01.nur (N.Urengoy)
13 - cr01.ndm (Nadym)
14 - cr01.nyg (Nyagan)
