bgpreport

Network · data from 2026-11-12

AS34056 KievNet

Registry name: KIEVNET Kyiv Optic Networks ltd, UA · PeeringDB

4IPv4 routes 75.0% RPKI valid · 75.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 0 origin · 1 maxLength
0No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS34056, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS34056, 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.
109.108.88.144/28 Invalid: maxLength Nonecovered by 109.108.64.0/19 1 0%low visibility 1
46.229.48.0/22 Valid RIR databaseRIPE 671 100% 68
92.244.96.0/19 Valid RIR databaseRIPE 671 100% 68
109.108.64.0/19 Valid RIR databaseRIPE 671 100% 68
2a00:1688::/48 Valid RIR databaseRIPE 636 100% 69

AS-SET

PeeringDB's irr_as_set for AS34056: AS-KIEVNET. 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 (AS34056 isn't in the set, or no route object for AS34056 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.

NameDatabaseASNsSets Route objectsAS34056 in itNot covered
AS-KIEVNET RIPE 298104 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 3 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength109.108.88.144/28ROA 109.108.64.0/19 AS34056 has maxLength 19; the route is a /28. Raise the maxLength, or add a ROA for 109.108.88.144/28.1 of 673
Route object: none109.108.88.144/28No route object for it. A route object for 109.108.64.0/19 with origin AS34056 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS34056 in the RIR database for the space.1 of 673

Route objects not announced

Route objects with origin AS34056 whose prefix no peer sees AS34056 announce. Many are kept on purpose (backup routes, space announced only in some places).

2a00:1688:1::/48RIPENo 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.