ResearchIRR · RIPE

AS-ROSTELECOM_MMT ASes routed by clients ROSTELECOM_MMT

An as-set registered in RIPE, maintained by OPS-MNT. It names 4 ASes and 1 set directly; followed all the way down, it reaches 4 ASes through 1 nested sets.

Members

What AS-ROSTELECOM_MMT lists

4 ASes and 1 set, written in the object across every registry that holds it. Sets open their own page. 1 of the sets is not registered in any IRR we mirror, so a filter built from AS-ROSTELECOM_MMT gets nothing from it.

AS-SET-NTLINE-RT not registeredAS8568 MMT-ASAS29554 SVYAZNOY-CHAIN-ASAS50511AS51971 SKOLKOVO
Expanded

Every AS it reaches

What a filter built from AS-ROSTELECOM_MMT would let in: 4 ASes.

Show the 4 ASes
AS8568AS29554AS50511AS51971
Prefixes

What AS-ROSTELECOM_MMT covers

Every route object in the IRR whose origin is one of the 4 ASes it reaches: the prefixes a filter built from AS-ROSTELECOM_MMT (with bgpq4, say) would allow. 13 IPv4 and 0 IPv6. Every one is in the IRR API.

13 IPv4 prefixes
195.166.160.0/24195.166.163.0/24195.166.176.0/23195.166.176.0/24195.166.180.0/22195.166.184.0/21195.166.184.0/22195.166.188.0/22195.166.189.0/24195.166.190.0/2487.226.149.0/2491.199.80.0/2491.220.219.0/24
Registries

Each registry’s copy

RIPE5 membersASes routed by clients ROSTELECOM_MMT
Maintained byOPS-MNT
Last modified2011-08-01T06:33:41Z
MembersAS8568 AS50511 AS29554 AS51971 AS-SET-NTLINE-RT
mbrs-by-refN
Tools

Check AS-ROSTELECOM_MMT live

IRR API, with prefixes