bgpreport

Network · data from 2026-11-12

AS8890 University of Warsaw

Registry name: UW-AS University of Warsaw, PL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8890, 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:6a0::/32 No ROA Other origin only 27 4%low visibility 15
193.0.64.0/18 No ROA RIR databaseRIPE 673 100% 66
212.87.0.0/20 No ROA RIR databaseRIPE 673 100% 66
2001:6a0:4000::/34 No ROA RIR databaseRIPE 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS8890: RIPE::AS8890:AS-IXP. 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 (AS8890 isn't in the set, or no route object for AS8890 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 objectsAS8890 in itNot covered
RIPE::AS8890:AS-IXP RIPE 118 Yes 1

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

  • ROA: none4
  • Route object: none1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none2001:6a0::/32No ROA covers it. Add a ROA for AS8890, maxLength 32.27 of 636
Route object: none2001:6a0::/32Route objects for it name AS8664. Add a route object with origin AS8890 in the RIR database for the space.27 of 636
ROA: none193.0.64.0/18No ROA covers it. Add a ROA for AS8890, maxLength 18.673 of 673
ROA: none212.87.0.0/20No ROA covers it. Add a ROA for AS8890, maxLength 20.673 of 673
ROA: none2001:6a0:4000::/34No ROA covers it. Add a ROA for AS8890, maxLength 34.635 of 636

Route objects not announced

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

193.0.64.0/19RIPENo ROA
193.0.96.0/19RIPENo ROA
212.87.0.0/21RIPENo ROA
212.87.8.0/21RIPENo ROA
213.135.63.0/24RIPENo 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.