Network · data from 2026-11-12

AS14650 NIC.BR f.dns.br

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

2IPv4 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

1Route objects not announced registered with origin AS14650, seen from no peer

Announced routes

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


200.219.158.0/24	Valid	Other IRR onlyRADB	673 100%	66
200.219.159.0/24	Valid	Other IRR onlyNTTCOM, RADB	665 99%	67
2001:12f8:c::/47	Valid	Other IRR onlyRADB	635 100%	70
2001:12f8:d::/48	Valid	Other IRR onlyRADB	635 100%	70
2001:12f8:c::/48	Valid	Other IRR onlyRADB	630 99%	70

AS-SET

PeeringDB's irr_as_set for AS14650: AS-DNS-BR:AS-F. 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 (AS14650 isn't in the set, or no route object for AS14650 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	AS14650 in it	Not covered
AS-DNS-BR:AS-F	RADB	1	1	6	Yes	0

Name

Database

ASNs

Sets

Route objects

AS14650 in it

Not covered

AS-DNS-BR:AS-F

RADB

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

Route object: RIR5
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	200.219.158.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	200.219.159.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	665 of 673
Route object: RIR	2001:12f8:c::/47	Route object only in RADB. Add it in the RIR database for the space.	635 of 636
Route object: RIR	2001:12f8:d::/48	Route object only in RADB. Add it in the RIR database for the space.	635 of 636
Route object: RIR	2001:12f8:c::/48	Route object only in RADB. Add it in the RIR database for the space.	630 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

200.219.158.0/24

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

673 of 673

Route object: RIR

200.219.159.0/24

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

665 of 673

Route object: RIR

2001:12f8:c::/47

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

635 of 636

Route object: RIR

2001:12f8:d::/48

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

635 of 636

Route object: RIR

2001:12f8:c::/48

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

630 of 636

Route objects not announced

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


200.219.158.0/23	RADB	Valid

200.219.158.0/23

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.