Network · data from 2026-11-12

AS200993 Yanislav Basiuk

Registry name: NyaCore Yanislav Basiuk, RU · PeeringDB

1IPv4 routes 100.0% RPKI valid · 100.0% with a route object

2IPv6 routes 50.0% RPKI valid · 100.0% with a route object

1RPKI invalid 0 origin · 1 maxLength

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

8Route objects not announced registered with origin AS200993, seen from no peer

Announced routes

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


2a12:4141:dc12::/48	Invalid: maxLength	RIR databaseRIPE	103 16%	36
91.193.111.0/24	Valid	RIR databaseRIPE	673 100%	67
2001:678:978::/48	Valid	RIR databaseRIPE	636 100%	67

AS-SET

PeeringDB's irr_as_set for AS200993: AS200993:AS-CORE. 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 (AS200993 isn't in the set, or no route object for AS200993 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	AS200993 in it	Not covered
AS200993:AS-CORE	RIPE1 member set in no database: AS199746:AS-NEXTSERV	133	38	1,523	Yes	0

Name

Database

ASNs

Sets

Route objects

AS200993 in it

Not covered

AS200993:AS-CORE

RIPE1 member set in no database: AS199746:AS-NEXTSERV

133

1,523

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 10 are in fix.csv.

ROA: maxLength1
AS-SET: missing member1
Route object: not announced8

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	2a12:4141:dc12::/48	ROA 2a12:4141::/32 AS200993 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2a12:4141:dc12::/48.	103 of 636
AS-SET: missing member	AS200993:AS-CORE	AS200993:AS-CORE (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

2a12:4141:dc12::/48

ROA 2a12:4141::/32 AS200993 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2a12:4141:dc12::/48.

103 of 636

AS-SET: missing member

AS200993:AS-CORE

AS200993:AS-CORE (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it.

Route objects not announced

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


2a06:de00:a0::/44	RIPE	No ROA
2a07:54c2:b00b::/48	RIPE	Valid
2a10:ccc1:1333::/48	RIPE	Invalid: origin
2a10:ccc1:1337::/48	RIPE	No ROA
2a12:4141::/32	RIPE	Valid
2a12:4141::/48	RIPE	Valid
2a12:4141:dead::/48	RIPE	Invalid: maxLength
2a12:4141:fa00::/40	RIPE	Valid

2a06:de00:a0::/44

RIPE

No ROA

2a07:54c2:b00b::/48

RIPE

Valid

2a10:ccc1:1333::/48

RIPE

Invalid: origin

2a10:ccc1:1337::/48

RIPE

No ROA

2a12:4141::/32

RIPE

Valid

2a12:4141::/48

RIPE

Valid

2a12:4141:dead::/48

RIPE

Invalid: maxLength

2a12:4141:fa00::/40

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.