bgpreport

Network · data from 2026-11-12

AS8256 LODMAN-AS Lodz University of Technology

Registry name: LODMAN-AS Lodz University of Technology, PL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8256, 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.
192.153.127.1/32 No ROA Nonecovered by 192.153.127.0/24 2 0%low visibility 3
192.153.127.0/24 No ROA RIR databaseRIPE 673 100% 67
212.51.192.0/21 Valid RIR databaseRIPE 673 100% 67
212.51.204.0/24 Valid RIR databaseRIPE 673 100% 67
212.51.207.0/24 Valid RIR databaseRIPE 673 100% 67
212.51.208.0/20 Valid RIR databaseRIPE 673 100% 67
212.191.0.0/17 Valid RIR databaseRIPE 673 100% 67
2001:b10::/35 Valid RIR databaseRIPE 635 100% 68

AS-SET

AS8256 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 3 are in fix.csv.

  • ROA: none2
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none192.153.127.1/32No ROA covers it. Add a ROA for AS8256, maxLength 32.2 of 673
Route object: none192.153.127.1/32No route object for it. A route object for 192.153.127.0/24 with origin AS8256 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS8256 in the RIR database for the space.2 of 673
ROA: none192.153.127.0/24No ROA covers it. Add a ROA for AS8256, maxLength 24.673 of 673

Route objects not announced

Every route object with origin AS8256 is announced.

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.