Network · data from 2026-11-12

AS264524 Cunha e Zanato telecom

Registry name: AS264524 - GIGA MAIS FIBRA TELECOMUNICACOES S.A., BR · PeeringDB

10IPv4 routes 90.0% RPKI valid · 30.0% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

1No ROA 8 with no route object for this origin

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

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

Announced routes

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


38.250.202.0/23	No ROA	Other IRR onlyRADB	671 100%	67
138.0.0.0/24	Valid	Nonecovered by 138.0.0.0/22	666 99%	67
138.0.1.0/24	Valid	Nonecovered by 138.0.0.0/22	666 99%	67
138.0.3.0/24	Valid	Nonecovered by 138.0.0.0/22	666 99%	67
2804:20f8:1000::/40	Valid	Nonecovered by 2804:20f8::/32	635 100%	67
170.247.36.0/24	Valid	Nonecovered by 170.247.36.0/22	127 19%	44
170.247.37.0/24	Valid	Nonecovered by 170.247.36.0/22	127 19%	44
170.247.38.0/24	Valid	Nonecovered by 170.247.36.0/22	127 19%	44
170.247.39.0/24	Valid	Nonecovered by 170.247.36.0/22	127 19%	44
138.0.0.0/22	Valid	Other IRR onlyNTTCOM, RADB, TC	671 100%	67
170.247.36.0/22	Valid	Other IRR onlyNTTCOM, RADB, TC	666 99%	67
2804:20f8::/32	Valid	Other IRR onlyRADB, TC	636 100%	67

AS-SET

AS264524'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 13 are in fix.csv.

ROA: none1
Route object: none8
Route object: RIR4

Change	Prefix or set	Detail	Full-table peers
ROA: none	38.250.202.0/23	No ROA covers it. Add a ROA for AS264524, maxLength 23.	671 of 673
Route object: RIR	38.250.202.0/23	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: none	138.0.0.0/24	No route object for it. A route object for 138.0.0.0/22 with origin AS264524 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264524 in the RIR database for the space.	666 of 673
Route object: none	138.0.1.0/24	No route object for it. A route object for 138.0.0.0/22 with origin AS264524 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264524 in the RIR database for the space.	666 of 673
Route object: none	138.0.3.0/24	No route object for it. A route object for 138.0.0.0/22 with origin AS264524 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264524 in the RIR database for the space.	666 of 673
Route object: none	2804:20f8:1000::/40	No route object for it. A route object for 2804:20f8::/32 with origin AS264524 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264524 in the RIR database for the space.	635 of 636
Route object: none	170.247.36.0/24	No route object for it. A route object for 170.247.36.0/22 with origin AS264524 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264524 in the RIR database for the space.	127 of 673
Route object: none	170.247.37.0/24	No route object for it. A route object for 170.247.36.0/22 with origin AS264524 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264524 in the RIR database for the space.	127 of 673
Route object: none	170.247.38.0/24	No route object for it. A route object for 170.247.36.0/22 with origin AS264524 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264524 in the RIR database for the space.	127 of 673
Route object: none	170.247.39.0/24	No route object for it. A route object for 170.247.36.0/22 with origin AS264524 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264524 in the RIR database for the space.	127 of 673
Route object: RIR	138.0.0.0/22	Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	170.247.36.0/22	Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.	666 of 673
Route object: RIR	2804:20f8::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	636 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

38.250.202.0/23

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

671 of 673

Route object: RIR

38.250.202.0/23

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

671 of 673

Route object: none

138.0.0.0/24

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

666 of 673

Route object: none

138.0.1.0/24

666 of 673

Route object: none

138.0.3.0/24

666 of 673

Route object: none

2804:20f8:1000::/40

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

635 of 636

Route object: none

170.247.36.0/24

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

127 of 673

Route object: none

170.247.37.0/24

127 of 673

Route object: none

170.247.38.0/24

127 of 673

Route object: none

170.247.39.0/24

127 of 673

Route object: RIR

138.0.0.0/22

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

671 of 673

Route object: RIR

170.247.36.0/22

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

666 of 673

Route object: RIR

2804:20f8::/32

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

636 of 636

Route objects not announced

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