bgpreport

Network · data from 2026-11-12

AS216024 KVMKA-COM ALEKSEI FEDOROV PR KRUSEVAC

Registry name: KVMKA-COM ALEKSEI FEDOROV PR KRUSEVAC, RS · not in PeeringDB

25IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 routes 66.7% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 0 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
14Route objects not announced registered with origin AS216024, seen from no peer

Announced routes

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

2a0f:cdc6:2030::/45 No ROA RIR databaseRIPE 1 0%low visibility 1
85.137.27.0/24 Valid RIR databaseRIPE 673 100% 67
146.255.188.0/24 Valid RIR databaseRIPE 673 100% 67
176.98.183.0/24 Valid RIR databaseRIPE 673 100% 67
176.98.191.0/24 Valid RIR databaseRIPE 673 100% 67
192.124.182.0/24 Valid RIR databaseRIPE 673 100% 66
192.124.190.0/24 Valid RIR databaseRIPE 673 100% 66
193.38.235.0/24 Valid RIR databaseRIPE 673 100% 67
193.124.203.0/24 Valid RIR databaseRIPE 673 100% 67
194.87.148.0/24 Valid RIR databaseRIPE 673 100% 66
194.87.189.0/24 Valid RIR databaseRIPE 673 100% 66
195.133.28.0/24 Valid RIR databaseRIPE 673 100% 66
217.65.79.0/24 Valid RIR databaseRIPE 673 100% 67
77.221.145.0/24 Valid RIR databaseRIPE 672 100% 67
45.129.143.0/24 Valid RIR databaseRIPE 671 100% 67
77.221.147.0/24 Valid RIR databaseRIPE 671 100% 68
85.137.24.0/24 Valid RIR databaseRIPE 671 100% 68
109.107.170.0/24 Valid RIR databaseRIPE 671 100% 67
109.107.171.0/24 Valid RIR databaseRIPE 671 100% 68
109.107.182.0/24 Valid RIR databaseRIPE 671 100% 68
193.233.22.0/24 Valid RIR databaseRIPE 671 100% 67
193.233.23.0/24 Valid RIR databaseRIPE 671 100% 68
194.58.36.0/24 Valid RIR databaseRIPE 671 100% 67
195.133.2.0/24 Valid RIR databaseRIPE 671 100% 68
195.133.26.0/24 Valid RIR databaseRIPE 671 100% 68
77.221.134.0/24 Valid RIR databaseRIPE 654 97% 67
2a12:6c40::/32 Valid RIR databaseRIPE 635 100% 69
2a11:c880::/29 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

AS216024 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 15 are in fix.csv.

  • ROA: none1
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none2a0f:cdc6:2030::/45No ROA covers it. Add a ROA for AS216024, maxLength 45.1 of 636

Route objects not announced

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

45.129.142.0/24RIPEValid
77.221.135.0/24RIPEInvalid: origin
85.137.25.0/24RIPEValid
85.137.26.0/24RIPEValid
109.120.145.0/24RIPEInvalid: origin
185.142.33.0/24RIPEValid
188.124.59.0/24RIPEValid
2a10:9681::/32RIPEValid
2a10:9682::/32RIPEValid
2a10:9683::/32RIPEValid
2a10:9687::/32RIPEValid
2a12:6c42::/32RIPEValid
2a12:6c43::/32RIPENo ROA
2a12:6c44::/32RIPENo ROA

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.