Network · data from 2026-11-12
AS48648 K-Link AS48648
Registry name: KYIVLINK K-Link LLC, UA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS48648, 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.
| 195.12.59.7/32 | Invalid: maxLength | Nonecovered by 195.12.56.0/22 | 2 0%low visibility |
| 195.12.59.0/24 | Valid | Nonecovered by 195.12.56.0/22 | 673 100% |
| 91.198.233.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.211.120.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.211.122.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.190.151.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.107.80.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.107.134.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.28.100.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.28.103.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.12.56.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 195.12.56.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.88.27.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a0a:2c0::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a0a:2c0:2::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a0a:2c0:a::/48 | Valid | RIR databaseRIPE | 632 99% |
AS-SET
PeeringDB's irr_as_set for AS48648: AS-KLNK. 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 (AS48648 isn't in the set, or no route object for AS48648 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 | AS48648 in it | Not covered |
|---|---|---|---|---|---|
| AS-KLNK | RIPElists itself further down | 185 | 49 | 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 4 are in fix.csv.
- ROA: maxLength1
- Route object: none2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 195.12.59.7/32 | ROA 195.12.56.0/22 AS48648 has maxLength 22; ROA 195.12.59.0/24 AS48648 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 195.12.59.7/32. |
| Route object: none | 195.12.59.7/32 | No route object for it. A route object for 195.12.56.0/22 with origin AS48648 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS48648 in the RIR database for the space. |
| Route object: none | 195.12.59.0/24 | No route object for it. A route object for 195.12.56.0/22 with origin AS48648 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48648 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS48648 whose prefix no peer sees AS48648 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 195.88.26.0/24 | RIPE | Invalid: origin |
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.