Network · data from 2026-11-12
AS197701 NET-KOMP Krystian Kania
Registry name: NET-KOMP-AS NET-KOMP Krystian Kania, PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS197701, 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.166.255.1/32 | Invalid: maxLength | Nonecovered by 192.166.255.0/24 | 3 0%low visibility |
| 185.228.57.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 46.245.232.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 192.166.255.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS197701: AS-SET:AS197701:AS-NETKOMP-EU. 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 (AS197701 isn't in the set, or no route object for AS197701 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.
| Name | Database | ASNs | Sets | AS197701 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-SET:AS197701:AS-NETKOMP-EU | In no IRR database read today. | |||||
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: maxLength1
- ROA: none1
- Route object: none1
- AS-SET: not found1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 192.166.255.1/32 | ROA 192.166.255.0/24 AS197701 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 192.166.255.1/32. |
| Route object: none | 192.166.255.1/32 | No route object for it. A route object for 192.166.255.0/24 with origin AS197701 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS197701 in the RIR database for the space. |
| ROA: none | 185.228.57.0/24 | No ROA covers it. Add a ROA for AS197701, maxLength 24. |
| AS-SET: not found | AS-SET:AS197701:AS-NETKOMP-EU | PeeringDB names AS-SET:AS197701:AS-NETKOMP-EU; no IRR database read has it. |
Route objects not announced
Route objects with origin AS197701 whose prefix no peer sees AS197701 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a10:f781:10:69e7::/64 | RIPE | No 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.