bgpreport

Network · data from 2026-11-12

AS11284 NIC.BR c.dns.br

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

3IPv4 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
0Route objects not announced registered with origin AS11284, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS11284, 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.192.232.0/23 Valid Other IRR onlyRADB 669 99% 68
200.192.232.0/24 Valid Other IRR onlyRADB 669 99% 68
200.192.233.0/24 Valid Other IRR onlyRADB 651 97% 68
2001:12f8:a::/47 Valid Other IRR onlyRADB 634 100% 70
2001:12f8:b::/48 Valid Other IRR onlyRADB 634 100% 70
2001:12f8:a::/48 Valid Other IRR onlyRADB 620 97% 70

AS-SET

PeeringDB's irr_as_set for AS11284: RADB::AS-DNS-BR:AS-C. 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 (AS11284 isn't in the set, or no route object for AS11284 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.

NameDatabaseASNsSets Route objectsAS11284 in itNot covered
RADB::AS-DNS-BR:AS-C RADB 116 Yes 0

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: RIR6
ChangePrefix or setDetailFull-table peers
Route object: RIR200.192.232.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR200.192.232.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR200.192.233.0/24Route object only in RADB. Add it in the RIR database for the space.651 of 673
Route object: RIR2001:12f8:a::/47Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2001:12f8:b::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2001:12f8:a::/48Route object only in RADB. Add it in the RIR database for the space.620 of 636

Route objects not announced

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