bgpreport

Network · data from 2026-11-12

AS202423 MGNHost-AS Tyurin Viktor Mihaylovich

Registry name: MGNHost-AS Tyurin Viktor Mihaylovich, RU · not in PeeringDB

19IPv4 routes 47.4% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
10No ROA 0 with no route object for this origin
8Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS202423, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS202423, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
45.128.184.0/24 No ROA RIR databaseRIPE 672 100% 66
45.128.185.0/24 No ROA RIR databaseRIPE 672 100% 66
45.128.186.0/24 No ROA RIR databaseRIPE 672 100% 66
45.128.187.0/24 No ROA RIR databaseRIPE 672 100% 66
185.29.124.0/24 No ROA RIR databaseRIPE 672 100% 66
185.29.126.0/24 No ROA RIR databaseRIPE 672 100% 66
185.29.127.0/24 No ROA RIR databaseRIPE 672 100% 66
91.132.196.0/24 No ROA RIR databaseRIPE 2 0%low visibility 2
45.151.232.0/24 No ROA RIR databaseRIPE 1 0%low visibility 1
185.180.108.0/24 No ROA RIR databaseRIPE 1 0%low visibility 1
77.220.205.0/24 Valid RIR databaseRIPE 672 100% 66
185.149.194.0/24 Valid RIR databaseRIPE 672 100% 66
193.233.31.0/24 Valid RIR databaseRIPE 672 100% 66
193.233.149.0/24 Valid RIR databaseRIPE 672 100% 66
185.180.109.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
193.0.178.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
193.0.179.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
193.233.174.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
193.233.72.0/24 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

AS202423 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 14 are in fix.csv.

  • ROA: none10
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none45.128.184.0/24No ROA covers it. Add a ROA for AS202423, maxLength 24.672 of 673
ROA: none45.128.185.0/24No ROA covers it. Add a ROA for AS202423, maxLength 24.672 of 673
ROA: none45.128.186.0/24No ROA covers it. Add a ROA for AS202423, maxLength 24.672 of 673
ROA: none45.128.187.0/24No ROA covers it. Add a ROA for AS202423, maxLength 24.672 of 673
ROA: none185.29.124.0/24No ROA covers it. Add a ROA for AS202423, maxLength 24.672 of 673
ROA: none185.29.126.0/24No ROA covers it. Add a ROA for AS202423, maxLength 24.672 of 673
ROA: none185.29.127.0/24No ROA covers it. Add a ROA for AS202423, maxLength 24.672 of 673
ROA: none91.132.196.0/24No ROA covers it. Add a ROA for AS202423, maxLength 24.2 of 673
ROA: none45.151.232.0/24No ROA covers it. Add a ROA for AS202423, maxLength 24.1 of 673
ROA: none185.180.108.0/24No ROA covers it. Add a ROA for AS202423, maxLength 24.1 of 673

Route objects not announced

Route objects with origin AS202423 whose prefix no peer sees AS202423 announce. Many are kept on purpose (backup routes, space announced only in some places).

2a0b:9080::/48RIPEValid
2a0b:9080:1::/48RIPEValid
2a0b:9080:2::/48RIPEValid
2a0b:9080:3::/48RIPEValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.