Network · data from 2026-11-12

AS11752 NIC.BR eventos

Registry name: AS11752 - Nucleo de Inf. e Coord. do Ponto BR - NIC.BR, BR · PeeringDB

3IPv4 routes 100.0% RPKI valid · 33.3% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 2 with no route object for this origin

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

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

Announced routes

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


189.76.96.0/20	Valid	Nonecovered by 189.76.96.0/19	2 0%low visibility	2
189.76.112.0/20	Valid	Nonecovered by 189.76.96.0/19	2 0%low visibility	2
189.76.96.0/19	Valid	Other IRR onlyRADB	668 99%	67
2001:12fe::/32	Valid	Other IRR onlyRADB	635 100%	67

189.76.96.0/20

Valid

Nonecovered by 189.76.96.0/19

2 0%low visibility

189.76.112.0/20

Valid

Nonecovered by 189.76.96.0/19

2 0%low visibility

189.76.96.0/19

Valid

Other IRR onlyRADB

668 99%

2001:12fe::/32

Valid

Other IRR onlyRADB

635 100%

AS-SET

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

Route object: none2
Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
Route object: none	189.76.96.0/20	No route object for it. A route object for 189.76.96.0/19 with origin AS11752 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11752 in the RIR database for the space.	2 of 673
Route object: none	189.76.112.0/20	No route object for it. A route object for 189.76.96.0/19 with origin AS11752 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11752 in the RIR database for the space.	2 of 673
Route object: RIR	189.76.96.0/19	Route object only in RADB. Add it in the RIR database for the space.	668 of 673
Route object: RIR	2001:12fe::/32	Route object only in RADB. Add it in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

189.76.96.0/20

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

2 of 673

Route object: none

189.76.112.0/20

2 of 673

Route object: RIR

189.76.96.0/19

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

668 of 673

Route object: RIR

2001:12fe::/32

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

635 of 636

Route objects not announced

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