ResearchIRR · RIPE

AS39718:AS-MIRTELECOM Mir Telecom Krasnodar

An as-set registered in RIPE, maintained by RU-MIR-TELECOM-1-MNT, MNT-IRBIS-TELECOMMUNICATIONS, MMPK-MNT. It names 2 ASes and 0 sets directly; followed all the way down, it reaches 2 ASes through 0 nested sets.

Members

What AS39718:AS-MIRTELECOM lists

2 ASes and 0 sets, written in the object across every registry that holds it. Sets open their own page.

AS39718 MIR-ASAS48129 IRBIS-TELECOMMUNICATIONS-AS
Expanded

Every AS it reaches

What a filter built from AS39718:AS-MIRTELECOM would let in: 2 ASes.

Show the 2 ASes
AS39718AS48129
Prefixes

What AS39718:AS-MIRTELECOM covers

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

17 IPv4 prefixes
81.30.112.0/2481.30.113.0/2481.30.114.0/2481.30.115.0/2481.30.116.0/2481.30.117.0/2481.30.118.0/2481.30.119.0/2481.30.120.0/2481.30.121.0/2481.30.122.0/2481.30.123.0/2481.30.124.0/2481.30.125.0/2481.30.126.0/2481.30.127.0/2491.210.44.0/22
Registries

Each registry’s copy

RIPE2 membersMir Telecom Krasnodar
Maintained byRU-MIR-TELECOM-1-MNT, MNT-IRBIS-TELECOMMUNICATIONS, MMPK-MNT
Last modified2024-04-15T09:31:14Z
MembersAS39718 AS48129
mbrs-by-refN
Tools

Check AS39718:AS-MIRTELECOM live

IRR API, with prefixes