bgpreport

Network · data from 2026-11-12

AS210751 IPLOG

Registry name: IPLOG Loginov Kirill Denisovich, RU · PeeringDB

16IPv4 routes 62.5% RPKI valid · 68.8% with a route object
0IPv6 routes
6RPKI invalid 6 origin · 0 maxLength
0No ROA 5 with no route object for this origin
6Low visibility seen by under 10% of full-table peers
7Route objects not announced registered with origin AS210751, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS210751, 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.

46.29.24.0/24 Invalid: origin None 2 0%low visibility 2
80.173.144.0/24 Invalid: origin None 2 0%low visibility 1
80.173.145.0/24 Invalid: origin None 2 0%low visibility 1
185.85.188.0/24 Invalid: origin None 2 0%low visibility 2
185.98.61.0/24 Invalid: origin None 2 0%low visibility 2
193.38.44.0/24 Invalid: origin RIR databaseRIPE 4 1%low visibility 3
85.28.59.0/24 Valid RIR databaseRIPE 673 100% 67
93.177.92.0/24 Valid RIR databaseRIPE 673 100% 67
45.140.5.0/24 Valid RIR databaseRIPE 672 100% 67
109.238.204.0/24 Valid RIR databaseRIPE 672 100% 67
193.160.72.0/24 Valid RIR databaseRIPE 672 100% 67
194.28.157.0/24 Valid RIR databaseRIPE 672 100% 67
77.83.23.0/24 Valid RIR databaseRIPE 671 100% 67
194.104.6.0/24 Valid RIR databaseRIPE 671 100% 67
200.163.81.0/24 Valid RIR databaseRIPE 653 97% 67
200.163.85.0/24 Valid RIR databaseRIPE 653 97% 67

AS-SET

AS210751's PeeringDB record names no 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 18 are in fix.csv.

  • ROA: origin6
  • Route object: none5
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: origin46.29.24.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS210751 should announce it, add a ROA for AS210751.2 of 673
Route object: none46.29.24.0/24No route object for it. Add a route object with origin AS210751 in the RIR database for the space.2 of 673
ROA: origin80.173.144.0/24ROAs covering it name AS209372, AS213541, not AS210751. If AS210751 should announce it, add a ROA for AS210751.2 of 673
Route object: none80.173.144.0/24No route object for it. Add a route object with origin AS210751 in the RIR database for the space.2 of 673
ROA: origin80.173.145.0/24ROAs covering it name AS209372, AS213541, not AS210751. If AS210751 should announce it, add a ROA for AS210751.2 of 673
Route object: none80.173.145.0/24No route object for it. Add a route object with origin AS210751 in the RIR database for the space.2 of 673
ROA: origin185.85.188.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS210751 should announce it, add a ROA for AS210751.2 of 673
Route object: none185.85.188.0/24No route object for it. Add a route object with origin AS210751 in the RIR database for the space.2 of 673
ROA: origin185.98.61.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS210751 should announce it, add a ROA for AS210751.2 of 673
Route object: none185.98.61.0/24No route object for it. Add a route object with origin AS210751 in the RIR database for the space.2 of 673
ROA: origin193.38.44.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS210751 should announce it, add a ROA for AS210751.4 of 673

Route objects not announced

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

94.187.192.0/24RIPEValid
94.187.193.0/24RIPEValid
94.187.194.0/24RIPEValid
94.187.195.0/24RIPEValid
94.187.196.0/24RIPEValid
94.187.197.0/24RIPEValid
94.187.198.0/24RIPEValid

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.