View

If you are scraping this block for the prefixes that a AS originates, please use the data dumps in https://bgp.tools/kb/api and cache them

	Prefix	Description
	2a02:ddc3::/48	-

---

Network Policy

Click here to learn more about what this graph means and what makes up a network policy Global Aggregation Policy nostalgic_nightingale

Chart Display Options

Display links using non straight lines

Prefixes in selected policy

Load all prefixes in policy

---

How are upstreams and downstreams calculated?

Upstreams

	ASN	Description	IPv4	IPv6
	AS47165	Omskie kabelnye seti Ltd.	✘	✔

---

Peers

	ASN	Description	IPv4	IPv6
	AS47165	Omskie kabelnye seti Ltd.	✘	✔

aut-num:        AS47246
as-name:        OmskTransitTelecom
org:            ORG-OL37-RIPE
import:         from AS47165 action pref=100; accept ANY
export:         to AS47165 announce AS-OMTT-SET
import:         from AS30729 action pref=100; accept AS-TRANSFER
export:         to AS30729 announce AS-OMTT-SET
import:         from AS41771 action pref=100; accept AS41771
export:         to AS41771 announce AS-OMTT-SET
import:         from AS41843 action pref=100; accept AS-ERTH
export:         to AS41843 announce AS-OMTT-SET
import:         from AS42676 action pref=100; accept AS42676
export:         to AS42676 announce AS-OMTT-SET
import:         from AS49880 action pref=100; accept AS49880
export:         to AS49880 announce AS-OMTT-SET
import:         from AS49404 action pref=100; accept AS49404
export:         to AS49404 announce AS-OMTT-SET
import:         from AS8411 action pref=100; accept AS8411
export:         to AS8411 announce AS-OMTT-SET
import:         from AS28884 action pref=100; accept AS28884
export:         to AS28884 announce AS-OMTT-SET
import:         from AS41440 action pref=100; accept AS41440
export:         to AS41440 announce AS-OMTT-SET
import:         from AS21127 action pref=100; accept AS21127
export:         to AS21127 announce AS-OMTT-SET
import:         from AS8402 action pref=100; accept AS8402
export:         to AS8402 announce AS-OMTT-SET
export:         to AS50928 announce AS-OMTT-SET
import:         from AS50928 action pref=100; accept AS50928
import:         from AS9049 action pref=100; accept AS-ERTH
export:         to AS9049 announce AS-OMTT-SET
import:         from AS31200 action pref=100; accept AS-RUNTK-SET
export:         to AS31200 announce AS-OMTT-SET
import:         from AS51028 action pref=100; accept AS-SVOLS
export:         to AS51028 announce AS-OMTT-SET
import:         from AS57629 action pref=100; accept AS-SVOLS
export:         to AS57629 announce AS-OMTT-SET
import:         from AS50923 action pref=100; accept AS-METRO-SET
export:         to AS50923 announce AS-OMTT-SET
import:         from AS199901 action pref=100; accept AS199901
export:         to AS199901 announce AS-OMTT-SET
import:         from AS15870 action pref=100; accept AS15870
export:         to AS15870 announce AS-OMTT-SET
import:         from AS57411 action pref=100; accept AS57411
export:         to AS57411 announce AS-OMTT-SET
import:         from AS50775 action pref=100; accept AS50775
export:         to AS50775 announce AS-OMTT-SET
import:         from AS57411 action pref=100; accept AS57411
export:         to AS57411 announce AS-OMTT-SET
import:         from AS43882 action pref=100; accept AS43882
export:         to AS43882 announce AS-OMTT-SET
mp-import:      afi ipv6.unicast from AS47165 action pref=100; accept ANY
mp-export:      afi ipv6.unicast to AS47165 announce AS47246
remarks:        ********************************************************
remarks:        You may use communities to control outgoing information
remarks:        via the route server. The meaning and order of remarks: evaluation is important:
remarks:        block announcement of a route to a certain peer 0:peer-as
remarks:        announcement of a route to a certain peer 47246:peer-as
remarks:        block announcement of a route to all peers 0:47246
remarks:        announcement of a route to all peers 47246:47246
remarks:        ********************************************************
admin-c:        DUMY-RIPE
tech-c:         DUMY-RIPE
status:         ASSIGNED
mnt-by:         RIPE-NCC-END-MNT
notify:         dmf@omkc.ru
mnt-by:         OmskTransitTelecom-mnt
created:        2008-05-23T12:08:09Z
last-modified:  2022-04-06T09:09:09Z
source:         RIPE
sponsoring-org: ORG-OksL1-RIPE
remarks:        ****************************
remarks:        * THIS OBJECT IS MODIFIED
remarks:        * Please note that all data that is generally regarded as personal
remarks:        * data has been removed from this object.
remarks:        * To view the original object, please query the RIPE Database at:
remarks:        * http://www.ripe.net/whois
remarks:        ****************************


organisation:   ORG-OL37-RIPE
org-name:       Omskie telekomunikacii Ltd.
country:        RU
org-type:       OTHER
address:        Dummy address for ORG-OL37-RIPE
# Email removed, Log into bgp.tools to see whois emails
mnt-ref:        OmskTransitTelecom-mnt
mnt-by:         OmskTransitTelecom-mnt
abuse-c:        AO3605-RIPE
created:        2008-04-14T12:53:48Z
last-modified:  2022-12-01T17:21:56Z
source:         RIPE
remarks:        ****************************
remarks:        * THIS OBJECT IS MODIFIED
remarks:        * Please note that all data that is generally regarded as personal
remarks:        * data has been removed from this object.
remarks:        * To view the original object, please query the RIPE Database at:
remarks:        * http://www.ripe.net/whois
remarks:        ****************************

Last Update: 2026-03-11T03:23:59Z UTC

---

Member of the following AS-SETs

-	Member	ASN Count
RIPE	as-omtt-set	17559
RADB	as-hurricanev6	20649
RIPE	as-omkc-set	16
RIPE	as-omkc-peering-set	132