bgpreport

Network · data from 2026-11-12

AS35213 TOV "Kompjuternie Merezhi"

Registry name: COMPNETUA-AS TOV "Kompjuternie Merezhi", UA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS35213, 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.201.168.0/24 Valid RIR databaseRIPE 671 100% 68
91.205.64.0/22 Valid RIR databaseRIPE 671 100% 68
91.239.136.0/22 Valid RIR databaseRIPE 671 100% 68
176.111.51.0/24 Valid RIR databaseRIPE 671 100% 68
193.0.247.0/24 Valid RIR databaseRIPE 671 100% 68
2001:678:31c::/48 Valid RIR databaseRIPE 635 100% 69
2a13:61c0::/29 Valid RIR databaseRIPE 634 100% 69
91.205.64.0/24 Valid RIR databaseRIPE 377 56% 61
91.205.65.0/24 Valid RIR databaseRIPE 377 56% 61
91.205.66.0/24 Valid RIR databaseRIPE 377 56% 61
91.205.67.0/24 Valid RIR databaseRIPE 377 56% 61
91.239.136.0/24 Valid RIR databaseRIPE 377 56% 61
91.239.138.0/24 Valid RIR databaseRIPE 377 56% 61

AS-SET

PeeringDB's irr_as_set for AS35213: AS-PCN AS-PCN-V6. 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 (AS35213 isn't in the set, or no route object for AS35213 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 objectsAS35213 in itNot covered
AS-PCN RIPElists itself further down1 member set in no database: AS-WINTELECOM 4816343 Yes 0
AS-PCN-V6 RIPE 7249 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
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberAS-PCNAS-PCN (RIPE) lists AS-WINTELECOM; no IRR database read has it.

Route objects not announced

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

91.239.137.0/24RIPEValid

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.