bgpreport

Network · data from 2026-11-12

AS206523 PUT Poznan University of Technology

Registry name: PUT Poznan University of Technology, PL · not in PeeringDB

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

Announced routes

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

2001:808:201::/64 Invalid: origin RIR databaseRIPE 1 0%low visibility 1
2001:808:201:4::/64 Invalid: origin RIR databaseRIPE 1 0%low visibility 1
2001:808:201:5::/64 Invalid: origin RIR databaseRIPE 1 0%low visibility 1
2001:808:201:6::/64 Invalid: origin RIR databaseRIPE 1 0%low visibility 1
2001:808:201:100::/64 Invalid: origin RIR databaseRIPE 1 0%low visibility 1
2001:808:201:101::/64 Invalid: origin RIR databaseRIPE 1 0%low visibility 1
2001:808:201:102::/64 Invalid: origin RIR databaseRIPE 1 0%low visibility 1
150.254.1.0/24 No ROA RIR databaseRIPE 673 100% 68
150.254.2.0/23 No ROA RIR databaseRIPE 673 100% 68
150.254.3.0/24 No ROA RIR databaseRIPE 673 100% 67
150.254.4.0/22 No ROA RIR databaseRIPE 673 100% 68
150.254.8.0/21 No ROA RIR databaseRIPE 673 100% 68
150.254.16.0/20 No ROA RIR databaseRIPE 673 100% 68
150.254.32.0/22 No ROA RIR databaseRIPE 673 100% 68
150.254.40.0/23 No ROA RIR databaseRIPE 673 100% 68
150.254.42.0/24 No ROA RIR databaseRIPE 673 100% 68
150.254.46.0/23 No ROA RIR databaseRIPE 673 100% 68
150.254.50.0/23 No ROA RIR databaseRIPE 673 100% 68
150.254.52.0/23 No ROA RIR databaseRIPE 673 100% 68
150.254.54.0/24 No ROA RIR databaseRIPE 673 100% 68
150.254.129.0/24 No ROA RIR databaseRIPE 673 100% 68
150.254.130.0/23 No ROA RIR databaseRIPE 673 100% 68
150.254.132.0/22 No ROA RIR databaseRIPE 673 100% 68
150.254.140.0/24 No ROA RIR databaseRIPE 673 100% 68

AS-SET

AS206523 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 30 are in fix.csv.

  • ROA: origin7
  • ROA: none17
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: origin2001:808:201::/64ROAs covering it name AS9112, not AS206523. If AS206523 should announce it, add a ROA for AS206523.1 of 636
ROA: origin2001:808:201:4::/64ROAs covering it name AS9112, not AS206523. If AS206523 should announce it, add a ROA for AS206523.1 of 636
ROA: origin2001:808:201:5::/64ROAs covering it name AS9112, not AS206523. If AS206523 should announce it, add a ROA for AS206523.1 of 636
ROA: origin2001:808:201:6::/64ROAs covering it name AS9112, not AS206523. If AS206523 should announce it, add a ROA for AS206523.1 of 636
ROA: origin2001:808:201:100::/64ROAs covering it name AS9112, not AS206523. If AS206523 should announce it, add a ROA for AS206523.1 of 636
ROA: origin2001:808:201:101::/64ROAs covering it name AS9112, not AS206523. If AS206523 should announce it, add a ROA for AS206523.1 of 636
ROA: origin2001:808:201:102::/64ROAs covering it name AS9112, not AS206523. If AS206523 should announce it, add a ROA for AS206523.1 of 636
ROA: none150.254.1.0/24No ROA covers it. Add a ROA for AS206523, maxLength 24.673 of 673
ROA: none150.254.2.0/23No ROA covers it. Add a ROA for AS206523, maxLength 23.673 of 673
ROA: none150.254.3.0/24No ROA covers it. Add a ROA for AS206523, maxLength 24.673 of 673
ROA: none150.254.4.0/22No ROA covers it. Add a ROA for AS206523, maxLength 22.673 of 673
ROA: none150.254.8.0/21No ROA covers it. Add a ROA for AS206523, maxLength 21.673 of 673
ROA: none150.254.16.0/20No ROA covers it. Add a ROA for AS206523, maxLength 20.673 of 673
ROA: none150.254.32.0/22No ROA covers it. Add a ROA for AS206523, maxLength 22.673 of 673
ROA: none150.254.40.0/23No ROA covers it. Add a ROA for AS206523, maxLength 23.673 of 673
ROA: none150.254.42.0/24No ROA covers it. Add a ROA for AS206523, maxLength 24.673 of 673
ROA: none150.254.46.0/23No ROA covers it. Add a ROA for AS206523, maxLength 23.673 of 673
ROA: none150.254.50.0/23No ROA covers it. Add a ROA for AS206523, maxLength 23.673 of 673
ROA: none150.254.52.0/23No ROA covers it. Add a ROA for AS206523, maxLength 23.673 of 673
ROA: none150.254.54.0/24No ROA covers it. Add a ROA for AS206523, maxLength 24.673 of 673
ROA: none150.254.129.0/24No ROA covers it. Add a ROA for AS206523, maxLength 24.673 of 673
ROA: none150.254.130.0/23No ROA covers it. Add a ROA for AS206523, maxLength 23.673 of 673
ROA: none150.254.132.0/22No ROA covers it. Add a ROA for AS206523, maxLength 22.673 of 673
ROA: none150.254.140.0/24No ROA covers it. Add a ROA for AS206523, maxLength 24.673 of 673

Route objects not announced

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

150.254.5.0/24RIPENo ROA
150.254.33.0/24RIPENo ROA
150.254.44.0/22RIPENo ROA
150.254.44.0/23RIPENo ROA
150.254.136.0/21RIPENo ROA
150.254.144.0/22RIPENo 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.