bgpreport

Network · data from 2026-11-12

AS12346 LUBMAN-COM-AS Maria Curie-Sklodowska University

Registry name: LUBMAN-COM-AS Maria Curie-Sklodowska University, PL · not in PeeringDB

12IPv4 routes 8.3% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
12No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
9Route objects not announced registered with origin AS12346, seen from no peer

Announced routes

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

2a04:444::/30 No ROA None 62 10%low visibility 22
87.246.224.0/20 No ROA RIR databaseRIPE 667 99% 68
192.188.233.0/24 No ROA RIR databaseRIPE 667 99% 68
212.182.80.0/20 No ROA RIR databaseRIPE 667 99% 68
212.182.96.0/19 No ROA RIR databaseRIPE 667 99% 68
212.182.97.0/24 No ROA RIR databaseRIPE 667 99% 68
212.182.100.0/22 No ROA RIR databaseRIPE 667 99% 68
212.182.108.0/24 No ROA RIR databaseRIPE 667 99% 68
212.182.114.0/24 No ROA RIR databaseRIPE 667 99% 68
212.182.116.0/24 No ROA RIR databaseRIPE 667 99% 68
212.182.117.0/24 No ROA RIR databaseRIPE 667 99% 68
212.182.118.0/24 No ROA RIR databaseRIPE 667 99% 68
192.188.235.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS12346 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 22 are in fix.csv.

  • ROA: none12
  • Route object: none1
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none2a04:444::/30No ROA covers it. Add a ROA for AS12346, maxLength 30.62 of 636
Route object: none2a04:444::/30No route object for it. Add a route object with origin AS12346 in the RIR database for the space.62 of 636
ROA: none87.246.224.0/20No ROA covers it. Add a ROA for AS12346, maxLength 20.667 of 673
ROA: none192.188.233.0/24No ROA covers it. Add a ROA for AS12346, maxLength 24.667 of 673
ROA: none212.182.80.0/20No ROA covers it. Add a ROA for AS12346, maxLength 20.667 of 673
ROA: none212.182.96.0/19No ROA covers it. Add a ROA for AS12346, maxLength 19.667 of 673
ROA: none212.182.97.0/24No ROA covers it. Add a ROA for AS12346, maxLength 24.667 of 673
ROA: none212.182.100.0/22No ROA covers it. Add a ROA for AS12346, maxLength 22.667 of 673
ROA: none212.182.108.0/24No ROA covers it. Add a ROA for AS12346, maxLength 24.667 of 673
ROA: none212.182.114.0/24No ROA covers it. Add a ROA for AS12346, maxLength 24.667 of 673
ROA: none212.182.116.0/24No ROA covers it. Add a ROA for AS12346, maxLength 24.667 of 673
ROA: none212.182.117.0/24No ROA covers it. Add a ROA for AS12346, maxLength 24.667 of 673
ROA: none212.182.118.0/24No ROA covers it. Add a ROA for AS12346, maxLength 24.667 of 673

Route objects not announced

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

87.246.232.0/21RIPENo ROA
87.246.232.0/24RIPENo ROA
212.182.63.16/28RIPEInvalid: origin
212.182.93.0/24RIPENo ROA
212.182.94.0/24RIPENo ROA
212.182.96.0/24RIPENo ROA
212.182.115.0/24RIPENo ROA
212.182.125.0/24RIPENo ROA
2a04:444::/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.