Network · data from 2026-11-12

AS266097 OKEY NET

Registry name: AS266097 - YUHOO NET, BR · PeeringDB

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

3IPv6 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

4Route objects not announced registered with origin AS266097, seen from no peer

Announced routes

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


45.4.176.0/23	Valid	Other IRR onlyRADB	671 100%	66
45.4.179.0/24	Valid	Other IRR onlyRADB	671 100%	67
45.4.177.0/24	Valid	Other IRR onlyRADB	670 100%	66
45.4.176.0/24	Valid	Other IRR onlyRADB	668 99%	66
2804:3a94::/32	Valid	Other IRR onlyRADB, TC	634 100%	69
2804:3a94::/33	Valid	Other IRR onlyRADB	634 100%	69
2804:3a94:8000::/33	Valid	Other IRR onlyRADB	634 100%	69

AS-SET

AS266097's PeeringDB record names no AS-SET.

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

Route object: RIR7
Route object: not announced4

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	45.4.176.0/23	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	45.4.179.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	45.4.177.0/24	Route object only in RADB. Add it in the RIR database for the space.	670 of 673
Route object: RIR	45.4.176.0/24	Route object only in RADB. Add it in the RIR database for the space.	668 of 673
Route object: RIR	2804:3a94::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	634 of 636
Route object: RIR	2804:3a94::/33	Route object only in RADB. Add it in the RIR database for the space.	634 of 636
Route object: RIR	2804:3a94:8000::/33	Route object only in RADB. Add it in the RIR database for the space.	634 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

45.4.176.0/23

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

671 of 673

Route object: RIR

45.4.179.0/24

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

671 of 673

Route object: RIR

45.4.177.0/24

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

670 of 673

Route object: RIR

45.4.176.0/24

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

668 of 673

Route object: RIR

2804:3a94::/32

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

634 of 636

Route object: RIR

2804:3a94::/33

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

634 of 636

Route object: RIR

2804:3a94:8000::/33

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

634 of 636

Route objects not announced

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


45.4.176.0/22	RADB	No ROA
45.4.178.0/23	RADB	No ROA
177.84.83.0/24	RADB	No ROA
2804:3a94::/34	RADB	Valid

45.4.176.0/22

RADB

No ROA

45.4.178.0/23

RADB

No ROA

177.84.83.0/24

RADB

No ROA

2804:3a94::/34

RADB

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.