Network · data from 2026-11-12

AS196906 WestNetwork AS196906

Registry name: WESTNET-AS PE Brunarsky Andrey Romanovich, UA · PeeringDB

3IPv4 routes 66.7% RPKI valid · 66.7% with a route object

0IPv6 routes

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

0Route objects not announced registered with origin AS196906, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS196906, 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.


78.25.4.0/24	Invalid: maxLength	Nonecovered by 78.25.4.0/23	18 3%low visibility	10
78.25.4.0/23	Valid	RIR databaseRIPE	671 100%	68
193.105.62.0/24	Valid	RIR databaseRIPE	671 100%	68

78.25.4.0/24

Invalid: maxLength

Nonecovered by 78.25.4.0/23

18 3%low visibility

78.25.4.0/23

Valid

RIR databaseRIPE

671 100%

193.105.62.0/24

Valid

RIR databaseRIPE

671 100%

AS-SET

PeeringDB's irr_as_set for AS196906: RIPE::AS-WESTNET-SET. 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 (AS196906 isn't in the set, or no route object for AS196906 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	Route objects	AS196906 in it	Not covered
RIPE::AS-WESTNET-SET	RIPE1 member set in no database: AS199986:AS-SET	4	2	8	Yes	0

Name

Database

ASNs

Sets

Route objects

AS196906 in it

Not covered

RIPE::AS-WESTNET-SET

RIPE1 member set in no database: AS199986:AS-SET

Yes

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
AS-SET: missing member1

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	78.25.4.0/24	ROA 78.25.4.0/23 AS196906 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 78.25.4.0/24.	18 of 673
Route object: none	78.25.4.0/24	No route object for it. A route object for 78.25.4.0/23 with origin AS196906 covers it (filters allowing more-specifics accept it). Add a route object with origin AS196906 in the RIR database for the space.	18 of 673
AS-SET: missing member	RIPE::AS-WESTNET-SET	AS-WESTNET-SET (RIPE) lists AS199986:AS-SET; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

78.25.4.0/24

ROA 78.25.4.0/23 AS196906 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 78.25.4.0/24.

18 of 673

Route object: none

78.25.4.0/24

No route object for it. A route object for 78.25.4.0/23 with origin AS196906 covers it (filters allowing more-specifics accept it). Add a route object with origin AS196906 in the RIR database for the space.

18 of 673

AS-SET: missing member

RIPE::AS-WESTNET-SET

AS-WESTNET-SET (RIPE) lists AS199986:AS-SET; no IRR database read has it.

Route objects not announced

Every route object with origin AS196906 is announced.

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.