bgpreport

Network · data from 2026-11-12

AS204930 Panstwowa Wyzsza Szkola Zawodowa w Nysie

Registry name: PWSZN-AS Panstwowa Akademia Nauk Stosowanych w Nysie, PL · PeeringDB

2IPv4 routes 0.0% RPKI valid · 50.0% with a route object
0IPv6 routes
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
2Route objects not announced registered with origin AS204930, seen from no peer

Announced routes

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

89.42.163.60/32 No ROA Nonecovered by 89.42.163.0/24 2 0%low visibility 6
89.42.163.0/24 No ROA RIR databaseRIPE 671 100% 68

AS-SET

PeeringDB's irr_as_set for AS204930: AS204930. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS204930 isn't in the set, or no route object for AS204930 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS204930 in itNot covered
AS204930 A single AS number, not a set: AS204930 (this network), 3 route objects.

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

  • ROA: none2
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none89.42.163.60/32No ROA covers it. Add a ROA for AS204930, maxLength 32.2 of 673
Route object: none89.42.163.60/32No route object for it. A route object for 89.42.163.0/24 with origin AS204930 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS204930 in the RIR database for the space.2 of 673
ROA: none89.42.163.0/24No ROA covers it. Add a ROA for AS204930, maxLength 24.671 of 673

Route objects not announced

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

2001:678:590::/48RIPENo ROA
2a10:f781:10:ddef::/64RIPENo 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.