Network · data from 2026-11-12

AS203493 Yacolo

Registry name: YACOLO-AS Egor Timoshenko, RU · PeeringDB

5IPv4 routes 60.0% RPKI valid · 100.0% with a route object

6IPv6 routes 66.7% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

4No ROA 0 with no route object for this origin

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS203493, 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.248.206.0/23	No ROA	RIR databaseRIPE	673 100%	66
46.8.251.0/24	No ROA	RIR databaseRIPE	672 100%	66
2a0d:d940:1200::/40	No ROA	RIR databaseRIPE	636 100%	67
2a0d:d940:1d00::/40	No ROA	RIR databaseRIPE	636 100%	67
89.37.193.0/24	Valid	RIR databaseRIPE	671 100%	68
194.87.209.0/24	Valid	RIR databaseRIPE	671 100%	68
194.226.42.0/24	Valid	RIR databaseRIPE	671 100%	68
2a09:6280:3::/48	Valid	RIR databaseRIPE	636 100%	68
2a0e:b107:2791::/48	Valid	RIR databaseRIPE	636 100%	68
2a0e:b107:2792::/48	Valid	RIR databaseRIPE	636 100%	68
2a0e:b107:2796::/48	Valid	RIR databaseRIPE	636 100%	68

AS-SET

PeeringDB's irr_as_set for AS203493: AS-YACOLO. 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 (AS203493 isn't in the set, or no route object for AS203493 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	AS203493 in it	Not covered
AS-YACOLO	RIPE	2	1	97	Yes	0

Name

Database

ASNs

Sets

Route objects

AS203493 in it

Not covered

AS-YACOLO

RIPE

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

ROA: none4

Change	Prefix or set	Detail	Full-table peers
ROA: none	109.248.206.0/23	No ROA covers it. Add a ROA for AS203493, maxLength 23.	673 of 673
ROA: none	46.8.251.0/24	No ROA covers it. Add a ROA for AS203493, maxLength 24.	672 of 673
ROA: none	2a0d:d940:1200::/40	No ROA covers it. Add a ROA for AS203493, maxLength 40.	636 of 636
ROA: none	2a0d:d940:1d00::/40	No ROA covers it. Add a ROA for AS203493, maxLength 40.	636 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

109.248.206.0/23

No ROA covers it. Add a ROA for AS203493, maxLength 23.

673 of 673

ROA: none

46.8.251.0/24

No ROA covers it. Add a ROA for AS203493, maxLength 24.

672 of 673

ROA: none

2a0d:d940:1200::/40

No ROA covers it. Add a ROA for AS203493, maxLength 40.

636 of 636

ROA: none

2a0d:d940:1d00::/40

No ROA covers it. Add a ROA for AS203493, maxLength 40.

636 of 636

Route objects not announced

Every route object with origin AS203493 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.