bgpreport

Network · data from 2026-11-12

AS263324 Net&Com Serviços de Informática e Telecomunicações Ltda

Registry name: AS263324 - Net&Com Servicos de Informatica e Telecomunicacoes, BR · PeeringDB

6IPv4 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
8Route objects not announced registered with origin AS263324, seen from no peer

Announced routes

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

170.247.20.0/22 Valid Other IRR onlyRADB 667 99% 66
177.86.156.0/22 Valid Other IRR onlyRADB, TC 667 99% 66
2804:1448::/32 Valid Other IRR onlyRADB, TC 629 99% 67
2804:1448::/33 Valid Other IRR onlyRADB 348 55% 64
2804:1448:8000::/33 Valid Other IRR onlyRADB 348 55% 64
170.247.20.0/23 Valid Other IRR onlyRADB 232 34% 57
177.86.156.0/23 Valid Other IRR onlyRADB 232 34% 57
177.86.158.0/23 Valid Other IRR onlyRADB, TC 232 34% 57
170.247.22.0/23 Valid Other IRR onlyRADB 231 34% 57

AS-SET

PeeringDB's irr_as_set for AS263324: AS263324:AS-NETECOM-ALL. 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 (AS263324 isn't in the set, or no route object for AS263324 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 objectsAS263324 in itNot covered
AS263324:AS-NETECOM-ALL RADBlists itself further down4 member sets in no database: AS-FIBERONE-ALL, AS-FNTTELECOM-ALL, AS-TRIBENET-ALL, AS264301:AS-LNP-TELECOM-ALL 79471,514 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 21 are in fix.csv.

  • Route object: RIR9
  • AS-SET: missing member4
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: RIR170.247.20.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR177.86.156.0/22Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:1448::/32Route object only in RADB, TC. Add it in the RIR database for the space.629 of 636
Route object: RIR2804:1448::/33Route object only in RADB. Add it in the RIR database for the space.348 of 636
Route object: RIR2804:1448:8000::/33Route object only in RADB. Add it in the RIR database for the space.348 of 636
Route object: RIR170.247.20.0/23Route object only in RADB. Add it in the RIR database for the space.232 of 673
Route object: RIR177.86.156.0/23Route object only in RADB. Add it in the RIR database for the space.232 of 673
Route object: RIR177.86.158.0/23Route object only in RADB, TC. Add it in the RIR database for the space.232 of 673
Route object: RIR170.247.22.0/23Route object only in RADB. Add it in the RIR database for the space.231 of 673
AS-SET: missing memberAS263324:AS-NETECOM-ALLAS263324:AS-NETECOM-ALL (RADB) lists AS-FIBERONE-ALL; no IRR database read has it.
AS-SET: missing memberAS263324:AS-NETECOM-ALLAS263324:AS-NETECOM-ALL (RADB) lists AS-FNTTELECOM-ALL; no IRR database read has it.
AS-SET: missing memberAS263324:AS-NETECOM-ALLAS263324:AS-NETECOM-ALL (RADB) lists AS-TRIBENET-ALL; no IRR database read has it.
AS-SET: missing memberAS263324:AS-NETECOM-ALLAS263324:AS-NETECOM-ALL (RADB) lists AS264301:AS-LNP-TELECOM-ALL; no IRR database read has it.

Route objects not announced

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

170.247.20.0/24RADBValid
170.247.21.0/24RADBValid
170.247.22.0/24RADBValid
170.247.23.0/24RADBValid
177.86.156.0/24RADB, TCValid
177.86.157.0/24RADB, TCValid
177.86.158.0/24RADB, TCValid
177.86.159.0/24RADB, TCValid

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.