Network · data from 2026-11-12
AS60646 LutekLAN.pl
Registry name: LUTEKLANPL-AS Krzysztof Sebastian Widerkiewicz trading as LutekLAN.pl, PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS60646, 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.
| 91.207.70.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 185.122.172.0/23 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS60646: AS60646. 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 (AS60646 isn't in the set, or no route object for AS60646 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 | AS60646 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS60646 | A single AS number, not a set: AS60646 (this network), 5 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 4 are in fix.csv.
- ROA: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.207.70.0/24 | No ROA covers it. Add a ROA for AS60646, maxLength 24. |
Route objects not announced
Route objects with origin AS60646 whose prefix no peer sees AS60646 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.122.172.0/24 | RIPE | Invalid: maxLength |
| 185.122.173.0/24 | RIPE | Invalid: maxLength |
| 2a10:f781:10:349d::/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.