Network · data from 2026-11-12

AS265466 Golfinho Internet

Registry name: AS265466 - Golfinho Internet, BR · PeeringDB

7IPv4 routes 100.0% RPKI valid · 42.9% with a route object

4IPv6 routes 100.0% RPKI valid · 25.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 7 with no route object for this origin

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

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

Announced routes

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


168.196.176.0/23	Valid	Nonecovered by 168.196.176.0/22	672 100%	67
168.196.178.0/23	Valid	Nonecovered by 168.196.176.0/22	672 100%	67
168.196.178.0/24	Valid	Nonecovered by 168.196.176.0/22	672 100%	67
168.196.179.0/24	Valid	Nonecovered by 168.196.176.0/22	672 100%	67
2804:3494::/33	Valid	Nonecovered by 2804:3494::/32	636 100%	67
2804:3494:2001::/48	Valid	Nonecovered by 2804:3494::/32	636 100%	67
2804:3494:8000::/33	Valid	Nonecovered by 2804:3494::/32	636 100%	67
168.196.176.0/22	Valid	Other IRR onlyTC	672 100%	67
168.196.176.0/24	Valid	Other IRR onlyRADB	672 100%	67
168.196.177.0/24	Valid	Other IRR onlyRADB	671 100%	67
2804:3494::/32	Valid	Other IRR onlyTC	636 100%	67

AS-SET

AS265466'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: none7
Route object: RIR4

Change	Prefix or set	Detail	Full-table peers
Route object: none	168.196.176.0/23	No route object for it. A route object for 168.196.176.0/22 with origin AS265466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265466 in the RIR database for the space.	672 of 673
Route object: none	168.196.178.0/23	No route object for it. A route object for 168.196.176.0/22 with origin AS265466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265466 in the RIR database for the space.	672 of 673
Route object: none	168.196.178.0/24	No route object for it. A route object for 168.196.176.0/22 with origin AS265466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265466 in the RIR database for the space.	672 of 673
Route object: none	168.196.179.0/24	No route object for it. A route object for 168.196.176.0/22 with origin AS265466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265466 in the RIR database for the space.	672 of 673
Route object: none	2804:3494::/33	No route object for it. A route object for 2804:3494::/32 with origin AS265466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265466 in the RIR database for the space.	636 of 636
Route object: none	2804:3494:2001::/48	No route object for it. A route object for 2804:3494::/32 with origin AS265466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265466 in the RIR database for the space.	636 of 636
Route object: none	2804:3494:8000::/33	No route object for it. A route object for 2804:3494::/32 with origin AS265466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265466 in the RIR database for the space.	636 of 636
Route object: RIR	168.196.176.0/22	Route object only in TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	168.196.176.0/24	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	168.196.177.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	2804:3494::/32	Route object only in TC. Add it in the RIR database for the space.	636 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

168.196.176.0/23

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

672 of 673

Route object: none

168.196.178.0/23

672 of 673

Route object: none

168.196.178.0/24

672 of 673

Route object: none

168.196.179.0/24

672 of 673

Route object: none

2804:3494::/33

No route object for it. A route object for 2804:3494::/32 with origin AS265466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265466 in the RIR database for the space.

636 of 636

Route object: none

2804:3494:2001::/48

636 of 636

Route object: none

2804:3494:8000::/33

636 of 636

Route object: RIR

168.196.176.0/22

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

672 of 673

Route object: RIR

168.196.176.0/24

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

672 of 673

Route object: RIR

168.196.177.0/24

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

671 of 673

Route object: RIR

2804:3494::/32

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

636 of 636

Route objects not announced

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