Routing security

AS39811 MTSNET-FAR-EAST-AS An Autonomous System for the Far East divisions

Unclassified RIPE

RPKI valid 36% 5 of 14 announcements

RPKI invalid 0 none

No ROA 9 not covered by any ROA

IRR registered 86% 0 missing · 2 other origin

ROAs 12 authorising this AS

Announcements

What this network originates

14 observed

Every prefix observed with AS39811 as its origin, checked against RPKI and the IRR. Problems sort first.

Prefix	RPKI	IRR	Vantage points
188.75.216.0/23	No ROA	IRR other origin	50
188.75.218.0/23	No ROA	IRR other origin	50
2a02:5f80::/32	No ROA	IRR	30
2a02:5f83::/32	No ROA	IRR	30
2a02:5f83:d0::/48	No ROA	IRR covering	30
2a02:5f83:d0cc::/48	No ROA	IRR covering	30
2a02:5f83:d1::/48	No ROA	IRR covering	30
2a02:5f83:d1cc::/48	No ROA	IRR covering	30
78.109.46.0/24	No ROA	IRR covering	51
85.140.127.0/24	RPKI valid	IRR	51
213.87.96.0/24	RPKI valid	IRR	51
213.87.97.0/24	RPKI valid	IRR	51
213.87.102.0/24	RPKI valid	IRR covering	51
213.87.103.0/24	RPKI valid	IRR covering	51

RPKI · ROAs

Route origin authorisations

12 ROAs

Signed statements by address holders that AS39811 may originate these prefixes, up to the maximum length shown.

Prefix	Max length	Trust anchor
85.140.127.0/24	/24	RIPENCC
213.87.96.0/24	/24	RIPENCC
213.87.97.0/24	/24	RIPENCC
213.87.98.0/23	/23	RIPENCC
213.87.100.0/24	/24	RIPENCC
213.87.101.0/24	/24	RIPENCC
213.87.102.0/24	/24	RIPENCC
213.87.103.0/24	/24	RIPENCC
213.87.104.0/24	/24	RIPENCC
213.87.105.0/24	/24	RIPENCC
213.87.106.0/23	/23	RIPENCC
213.87.246.0/24	/24	RIPENCC

ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.

RPKI · ASPA

Declared transit providers

No ASPA record This network has not published an ASPA object. ASPA lets a network sign the list of its transit providers, so routers can reject paths that route through anyone else (route leaks). Only a few thousand networks publish one so far, so its absence is normal.

IRR

Registered route objects

31 objects · 26 not announced

Route objects naming AS39811 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.

Prefix	Source	Description	Maintainer	Changed	Routing
46.232.166.0/23	RIPE	MTS Vladivostok	`MTU-NOC`	2020-07-24	Not announced
46.232.166.0/24	RIPE	MTS Vladivostok	`MTU-NOC`	2020-07-22	Not announced
77.220.60.0/23	RIPE	MTS Vladivostok route object	`MTU-NOC`	2021-10-01	Not announced
78.109.46.0/23	RIPE	MTS DV	`MR-DV-MTS-MNT`	2015-08-18	Not announced
80.83.228.0/22	RIPE	Mobile TeleSystems, OJSC, MR DV	`MR-DV-MTS-MNT`	2008-06-02	Not announced
80.83.232.0/22	RIPE	Mobile TeleSystems, OJSC, MR DV	`MR-DV-MTS-MNT`	2008-06-02	Not announced
80.83.236.0/22	RIPE	Mobile TeleSystems, OJSC, MR DV	`MR-DV-MTS-MNT`	2008-06-02	Not announced
80.83.237.0/24	RIPE	Mobile TeleSystems, OJSC, MR DV	`MR-DV-MTS-MNT`	2010-02-07	Not announced
80.83.238.0/24	RIPE	Mobile TeleSystems, OJSC, MR DV	`MR-DV-MTS-MNT`	2010-02-04	Not announced
80.83.239.0/24	RIPE	Mobile TeleSystems, OJSC, MR DV	`MR-DV-MTS-MNT`	2010-02-04	Not announced
81.195.239.0/24	RIPE	Mobile TeleSystems, PJSC, Far East	`MTU-NOC`	2018-06-19	Not announced
89.22.190.0/23	RIPE	MTS Vladivostok	`MTU-NOC`	2019-05-16	Not announced
176.118.14.0/23	RIPE	Mobile TeleSystems PJSC, Far-East division	`MTU-NOC`	2018-09-04	Not announced
185.59.137.0/24	RIPE	MTS Yakutsk broadband network	`MR-DV-MTS-MNT`	2017-06-14	Not announced
212.188.15.0/24	RIPE	Google net MTS MRDV	`MR-DV-MTS-MNT`	2013-02-20	Not announced
213.87.96.0/23	RIPE	Vladivostok (Far East) division of Mobile Telesystems OJSC	`MR-DV-MTS-MNT`	2008-05-15	Not announced
213.87.98.0/23	RIPE	Primorye division of Mobile Telesystems OJSC	`MR-DV-MTS-MNT`	2012-12-25	Not announced
213.87.100.0/22	RIPE	MR DV division of Mobile Telesystems OJSC	`MR-DV-MTS-MNT`	2011-06-01	Not announced
213.87.100.0/24	RIPE	MR DV division of Mobile Telesystems OJSC	`MR-DV-MTS-MNT`	2011-09-08	Not announced
213.87.104.0/23	RIPE	Vladivostok division of Mobile Telesystems OJSC	`MR-DV-MTS-MNT`	2012-08-01	Not announced
213.87.104.0/24	RIPE	Vladivostok division of Mobile Telesystems OJSC	`MTU-NOC`	2021-11-12	Not announced
213.87.106.0/23	RIPE	Vladivostok division of Mobile Telesystems OJSC	`MR-DV-MTS-MNT`	2012-09-06	Not announced
213.87.108.0/23	RIPE	Vladivostok division of Mobile Telesystems OJSC	`MR-DV-MTS-MNT`	2012-09-06	Not announced
213.87.110.0/23	RIPE	Vladivostok division of Mobile Telesystems OJSC	`MR-DV-MTS-MNT`	2012-09-06	Not announced
213.87.246.0/24	RIPE	MTS PJSC Far-East	`MTU-NOC`	2017-12-19	Not announced
2a02:28:8::/47	RIPE	MR DV division of Mobile Telesystems OJSC	`MTU-NOC`	2014-01-21	Not announced
85.140.127.0/24	RIPE	MTS Blagoveschensk	`MTU-NOC`	2018-05-15	Announced
213.87.96.0/24	RIPE	Vladivostok (Far East) division of Mobile Telesystems OJSC	`MR-DV-MTS-MNT`	2011-11-20	Announced
213.87.97.0/24	RIPE	Vladivostok (Far East) division of Mobile Telesystems OJSC	`MR-DV-MTS-MNT`	2011-11-17	Announced
2a02:5f80::/32	RIPE	MTS-Blagoveschensk-ipv6-net	`MTU-NOC`	2020-10-14	Announced
2a02:5f83::/32	RIPE	MTS Ulan-Ude Fixed Broadband Network ipv6-net	`MTU-NOC`	2020-11-25	Announced

IRR

AS-sets

The as-set is what upstreams expand to build this network's customer filter. Sets that list AS39811 directly show who expects to carry it.

AS-set	Where	Relationship
`AS-BLOCK-SET`	RIPE	Lists AS39811 as a direct member
`AS-BLOCKED-RU`	RIPE	Lists AS39811 as a direct member
`AS-DDK35`	RIPE	Lists AS39811 as a direct member
`AS-INTER-COM`	RIPE	Lists AS39811 as a direct member
`AS-MTS-SAKH`	RIPE	Lists AS39811 as a direct member
`AS-MTSDV`	RIPE	Lists AS39811 as a direct member
`AS-MTU`	RIPE	Lists AS39811 as a direct member
`AS-MTU2`	RIPE	Lists AS39811 as a direct member
`AS-SATISNET-KHB`	RIPE	Lists AS39811 as a direct member
`AS-SIBNET`	RIPE	Lists AS39811 as a direct member
`AS34251:AS-RUFILE`	RIPE	Lists AS39811 as a direct member

RPKI from rpki-client, validated 2026-10-14 18:17 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-14. Cross-check on bgp.he.net.