Network · data from 2026-11-12

AS266777 DOVAL MANUEL ANGEL (INETGAMING)

Registry name: AS266777 - DOVAL MANUEL ANGEL (INETGAMING), AR · PeeringDB

12IPv4 routes 91.7% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

1No 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 AS266777, seen from no peer

Announced routes

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


23.175.40.0/23	No ROA	Other IRR onlyRADB	666 99%	67
142.249.120.0/22	Valid	RIR databaseARIN	671 100%	67
142.249.120.0/24	Valid	RIR databaseARIN	671 100%	67
142.249.121.0/24	Valid	RIR databaseARIN	671 100%	67
142.249.122.0/24	Valid	RIR databaseARIN	671 100%	67
142.249.123.0/24	Valid	RIR databaseARIN	671 100%	67
45.235.98.0/23	Valid	RIR databaseLACNIC, RADB	669 99%	67
160.20.247.0/24	Valid	RIR databaseLACNIC, RADB	660 98%	67
23.175.41.0/24	Valid	RIR databaseARIN, RADB	658 98%	67
23.175.40.0/24	Valid	RIR databaseARIN, RADB	657 98%	67
45.235.99.0/24	Valid	RIR databaseLACNIC, RADB	657 98%	67
45.235.98.0/24	Valid	RIR databaseLACNIC, RADB	656 97%	67

AS-SET

PeeringDB's irr_as_set for AS266777: AS266777:AS-INETGAMING. 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 (AS266777 isn't in the set, or no route object for AS266777 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	AS266777 in it	Not covered
AS266777:AS-INETGAMING	LACNIC	9	9	2,463	Yes	0

Name

Database

ASNs

Sets

Route objects

AS266777 in it

Not covered

AS266777:AS-INETGAMING

LACNIC

2,463

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: none1
Route object: RIR1
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
ROA: none	23.175.40.0/23	No ROA covers it. Add a ROA for AS266777, maxLength 23.	666 of 673
Route object: RIR	23.175.40.0/23	Route object only in RADB. Add it in the RIR database for the space.	666 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

23.175.40.0/23

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

666 of 673

Route object: RIR

23.175.40.0/23

Route object only in RADB. Add it in the RIR database for the space.

666 of 673

Route objects not announced

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


2803:1f20::/32	RADB	No ROA

2803:1f20::/32

RADB

No 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.