Network · data from 2026-11-12
AS197726 Ukrainian Internet Names Center
Registry name: UKRNAMES-AS Ukrainian Internet Names Center LTD, UA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS197726, 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.231.85.113/32 | Invalid: maxLength | Nonecovered by 91.231.84.0/23 | 3 0%low visibility |
| 195.123.178.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 195.123.193.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 195.123.194.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 195.123.195.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 91.231.84.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 91.231.86.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 185.112.12.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 185.112.14.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 193.9.28.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.64.154.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 195.88.243.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 212.86.110.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 212.86.111.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 212.86.113.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2a02:128:2::/48 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS197726: AS-UKRNAMES. 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 (AS197726 isn't in the set, or no route object for AS197726 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 | AS197726 in it | Not covered |
|---|---|---|---|---|---|
| AS-UKRNAMES | RIPE | 3 | 1 | 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 11 are in fix.csv.
- ROA: maxLength1
- ROA: none4
- Route object: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 91.231.85.113/32 | ROA 91.231.84.0/23 AS197726 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 91.231.85.113/32. |
| Route object: none | 91.231.85.113/32 | No route object for it. A route object for 91.231.84.0/23 with origin AS197726 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS197726 in the RIR database for the space. |
| ROA: none | 195.123.178.0/24 | No ROA covers it. Add a ROA for AS197726, maxLength 24. |
| ROA: none | 195.123.193.0/24 | No ROA covers it. Add a ROA for AS197726, maxLength 24. |
| ROA: none | 195.123.194.0/24 | No ROA covers it. Add a ROA for AS197726, maxLength 24. |
| ROA: none | 195.123.195.0/24 | No ROA covers it. Add a ROA for AS197726, maxLength 24. |
Route objects not announced
Route objects with origin AS197726 whose prefix no peer sees AS197726 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 195.123.176.0/24 | RIPE | No ROA |
| 195.123.179.0/24 | RIPE | No ROA |
| 195.123.184.0/22 | RIPE | No ROA |
| 195.123.187.0/24 | RIPE | No ROA |
| 195.123.248.0/22 | 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.