Network · data from 2026-11-12
AS8695 Kherson Traffic Exchange
Registry name: KS-IX-AS Private Enterprise "Law Firm "Status", UA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS8695, 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:7f8:80::/48 | Valid | RIR databaseRIPE | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS8695: RIPE::AS-KS-IX. 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 (AS8695 isn't in the set, or no route object for AS8695 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 | AS8695 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-KS-IX | RIPElists itself further down1 member set in no database: AS-WINTELECOM | 48 | 16 | Yes | 0 |
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 2 are in fix.csv.
- AS-SET: missing member1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: missing member | RIPE::AS-KS-IX | AS-KS-IX (RIPE) lists AS-WINTELECOM; no IRR database read has it. |
Route objects not announced
Route objects with origin AS8695 whose prefix no peer sees AS8695 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.1.39.0/24 | RIPE | Valid |
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.