bgpreport

Network · data from 2026-11-12

AS263016 NDX Telecomunicacoes Ltda

Registry name: AS263016 - NDX Net Servicos de Informatica Ltda., BR · PeeringDB

3IPv4 routes 33.3% RPKI valid · 66.7% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS263016, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS263016, 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.
38.211.28.0/22 No ROA None 80 12% 34
38.211.12.0/22 No ROA Other IRR onlyRADB 670 100% 66
177.10.152.0/22 Valid Other IRR onlyRADB, TC 670 100% 67
2804:a0c::/32 Valid Other IRR onlyRADB, TC 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS263016: AS-NDXNET. 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 (AS263016 isn't in the set, or no route object for AS263016 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 objectsAS263016 in itNot covered
AS-NDXNET In no IRR database read today.

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

  • ROA: none2
  • Route object: none1
  • Route object: RIR3
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: none38.211.28.0/22No ROA covers it. Add a ROA for AS263016, maxLength 22.80 of 673
Route object: none38.211.28.0/22No route object for it. Add a route object with origin AS263016 in the RIR database for the space.80 of 673
ROA: none38.211.12.0/22No ROA covers it. Add a ROA for AS263016, maxLength 22.670 of 673
Route object: RIR38.211.12.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR177.10.152.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:a0c::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
AS-SET: not foundAS-NDXNETPeeringDB names AS-NDXNET; no IRR database read has it.

Route objects not announced

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