bgpreport

Network · data from 2026-11-12

AS30836 NET23VNet

Registry name: NET23-AS 23VNet Kft., HU · PeeringDB

11IPv4 routes 18.2% RPKI valid · 72.7% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
9No ROA 3 with no route object for this origin
8Low visibility seen by under 10% of full-table peers
13Route objects not announced registered with origin AS30836, seen from no peer

Announced routes

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

217.112.130.0/24 No ROA Other origin onlycovered by 217.112.128.0/20 2 0%low visibility 2
217.112.134.0/23 No ROA Other origin onlycovered by 217.112.128.0/20 2 0%low visibility 2
217.112.136.0/23 No ROA Other origin onlycovered by 217.112.128.0/20 2 0%low visibility 2
193.188.140.0/23 No ROA RIR databaseRIPE 672 100% 66
217.112.129.0/24 No ROA RIR databaseRIPE 2 0%low visibility 2
217.112.131.0/24 No ROA RIR databaseRIPE 2 0%low visibility 2
217.112.132.0/24 No ROA RIR databaseRIPE 2 0%low visibility 2
217.112.140.0/24 No ROA RIR databaseRIPE 2 0%low visibility 2
217.112.141.0/24 No ROA RIR databaseRIPE 2 0%low visibility 2
195.56.101.0/24 Valid RIR databaseRIPE 672 100% 66
217.113.62.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS30836'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 25 are in fix.csv.

  • ROA: none9
  • Route object: none3
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: none217.112.130.0/24No ROA covers it. Add a ROA for AS30836, maxLength 24.2 of 673
Route object: none217.112.130.0/24Route objects for it name AS41075. A route object for 217.112.128.0/20 with origin AS30836 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30836 in the RIR database for the space.2 of 673
ROA: none217.112.134.0/23No ROA covers it. Add a ROA for AS30836, maxLength 23.2 of 673
Route object: none217.112.134.0/23Route objects for it name AS41075. A route object for 217.112.128.0/20 with origin AS30836 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30836 in the RIR database for the space.2 of 673
ROA: none217.112.136.0/23No ROA covers it. Add a ROA for AS30836, maxLength 23.2 of 673
Route object: none217.112.136.0/23Route objects for it name AS41075. A route object for 217.112.128.0/20 with origin AS30836 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30836 in the RIR database for the space.2 of 673
ROA: none193.188.140.0/23No ROA covers it. Add a ROA for AS30836, maxLength 23.672 of 673
ROA: none217.112.129.0/24No ROA covers it. Add a ROA for AS30836, maxLength 24.2 of 673
ROA: none217.112.131.0/24No ROA covers it. Add a ROA for AS30836, maxLength 24.2 of 673
ROA: none217.112.132.0/24No ROA covers it. Add a ROA for AS30836, maxLength 24.2 of 673
ROA: none217.112.140.0/24No ROA covers it. Add a ROA for AS30836, maxLength 24.2 of 673
ROA: none217.112.141.0/24No ROA covers it. Add a ROA for AS30836, maxLength 24.2 of 673

Route objects not announced

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

87.229.102.0/23RIPENo ROA
91.120.36.0/24RIPEInvalid: origin
94.199.48.0/21RIPENo ROA
185.188.56.0/24RIPENo ROA
185.188.57.0/24RIPENo ROA
185.225.68.0/22RIPENo ROA
195.56.170.0/24RIPEInvalid: origin
195.56.172.0/24RIPEInvalid: origin
217.112.128.0/20RIPENo ROA
217.112.138.0/24RIPENo ROA
2a02:c640::/32RIPENo ROA
2a03:8c60:1::/48RIPENo ROA
2a0b:b980:1::/48RIPENo 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.