Network · data from 2026-11-12

AS53163 CONID - CIA NACIONAL PARA INCLUSAO DIGITAL

Registry name: AS53163 - CONID - Companhia Naciona para Inclusao Digital, BR · PeeringDB

5IPv4 routes 80.0% RPKI valid · 80.0% with a route object

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

1RPKI invalid 1 origin · 0 maxLength

0No ROA 1 with no route object for this origin

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

522Route objects not announced registered with origin AS53163, seen from no peer

Announced routes

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


45.6.114.0/23	Invalid: origin	Other origin only	73 11%	36
177.137.190.0/23	Valid	Other IRR onlyRADB, TC	672 100%	67
177.137.191.0/24	Valid	Other IRR onlyRADB, TC	672 100%	67
187.1.112.0/20	Valid	Other IRR onlyRADB, TC	672 100%	67
187.1.113.0/24	Valid	Other IRR onlyRADB, TC	672 100%	67
2804:1030::/32	Valid	Other IRR onlyRADB, TC	635 100%	69
2804:1030:8000::/36	Valid	Other IRR onlyRADB	635 100%	69

AS-SET

PeeringDB's irr_as_set for AS53163: TC::AS53163. 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 (AS53163 isn't in the set, or no route object for AS53163 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	AS53163 in it	Not covered
TC::AS53163	A single AS number, not a set: AS53163 (this network), 528 route objects.

Name

Database

ASNs

Sets

Route objects

AS53163 in it

Not covered

TC::AS53163

A single AS number, not a set: AS53163 (this network), 528 route objects.

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

ROA: origin1
Route object: none1
Route object: RIR6
Route object: not announced522

Change	Prefix or set	Detail	Full-table peers
ROA: origin	45.6.114.0/23	ROAs covering it name AS266131, not AS53163. If AS53163 should announce it, add a ROA for AS53163.	73 of 673
Route object: none	45.6.114.0/23	Route objects for it name AS266131. Add a route object with origin AS53163 in the RIR database for the space.	73 of 673
Route object: RIR	177.137.190.0/23	Route object only in RADB, TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	177.137.191.0/24	Route object only in RADB, TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	187.1.112.0/20	Route object only in RADB, TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	187.1.113.0/24	Route object only in RADB, TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	2804:1030::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	635 of 636
Route object: RIR	2804:1030:8000::/36	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

ROA: origin

45.6.114.0/23

ROAs covering it name AS266131, not AS53163. If AS53163 should announce it, add a ROA for AS53163.

73 of 673

Route object: none

45.6.114.0/23

Route objects for it name AS266131. Add a route object with origin AS53163 in the RIR database for the space.

73 of 673

Route object: RIR

177.137.190.0/23