bgpreport

Network · data from 2026-11-12

AS401322 NetO Corp

Registry name: LUCK-NETO-01 - NetO Corp, US · PeeringDB

40IPv4 routes 82.5% RPKI valid · 62.5% with a route object
1IPv6 routes 0.0% RPKI valid · 0.0% with a route object
2RPKI invalid 2 origin · 0 maxLength
6No ROA 16 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
10Route objects not announced registered with origin AS401322, seen from no peer

Announced routes

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

66.117.159.0/24 Invalid: origin Other origin only 2 0%low visibility 2
109.176.134.0/24 Invalid: origin Other origin only 2 0%low visibility 2
38.134.104.0/24 No ROA Nonecovered by 38.134.104.0/23 669 99% 66
38.134.105.0/24 No ROA Nonecovered by 38.134.104.0/23 669 99% 66
2602:f7cf::/48 No ROA Nonecovered by 2602:f7cf::/40 635 100% 67
206.109.66.0/23 No ROA RIR databaseARIN 670 100% 66
206.109.82.0/24 No ROA RIR databaseARIN 670 100% 66
38.123.174.0/24 No ROA RIR databaseARIN 2 0%low visibility 2
189.13.1.0/24 Valid None 673 100% 66
189.13.163.0/24 Valid None 673 100% 67
189.13.248.0/24 Valid None 673 100% 67
189.13.249.0/24 Valid None 673 100% 67
189.13.250.0/24 Valid None 673 100% 67
189.13.252.0/24 Valid None 673 100% 67
189.13.253.0/24 Valid None 673 100% 67
189.13.254.0/24 Valid None 673 100% 66
189.13.255.0/24 Valid None 673 100% 66
189.13.251.0/24 Valid None 671 100% 67
189.13.50.0/24 Valid None 667 99% 66
77.107.82.0/24 Valid Other IRR onlyRADB 672 100% 67
66.253.70.0/24 Valid RIR databaseARIN 673 100% 67
66.253.84.0/24 Valid RIR databaseARIN 673 100% 67
66.253.86.0/24 Valid RIR databaseARIN 673 100% 67
185.228.2.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
216.132.68.0/24 Valid RIR databaseARIN 673 100% 67
216.132.71.0/24 Valid RIR databaseARIN 673 100% 67
216.132.74.0/24 Valid RIR databaseARIN 673 100% 67
216.132.94.0/24 Valid RIR databaseARIN 673 100% 67
216.132.149.0/24 Valid RIR databaseARIN 673 100% 67
109.121.39.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
168.222.25.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
37.230.53.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
185.199.213.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
201.14.221.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
66.92.62.0/24 Valid RIR databaseARIN, RADB 670 100% 66
66.93.5.0/24 Valid RIR databaseARIN 670 100% 67
82.21.84.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
206.206.88.0/24 Valid RIR databaseARIN, RADB 670 100% 66
163.5.47.0/24 Valid RIR databaseRADB, RIPE 669 99% 66
66.17.143.0/24 Valid RIR databaseARIN 640 95% 67
149.12.179.0/24 Valid RIR databaseARIN 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS401322: RADB::AS401322:AS-GLOBAL. 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 (AS401322 isn't in the set, or no route object for AS401322 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 objectsAS401322 in itNot covered
RADB::AS401322:AS-GLOBAL RADB8 member sets in no database: AS-EOIX, AS-IDCCUBE, AS199310:AS-QFNET, AS199436:AS-AUBREY, AS199436:AS-CUSTOMER-LAIN … 216315,811 Yes 13

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

  • ROA: origin2
  • ROA: none6
  • Route object: none16
  • Route object: RIR1
  • AS-SET: missing member8
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: origin66.117.159.0/24ROAs covering it name AS834, AS7235, not AS401322. If AS401322 should announce it, add a ROA for AS401322.2 of 673
Route object: none66.117.159.0/24Route objects for it name AS834. Add a route object with origin AS401322 in the RIR database for the space.2 of 673
ROA: origin109.176.134.0/24ROAs covering it name AS834, AS8851, AS19905, AS206509, not AS401322. If AS401322 should announce it, add a ROA for AS401322.2 of 673
Route object: none109.176.134.0/24Route objects for it name AS834. Add a route object with origin AS401322 in the RIR database for the space.2 of 673
ROA: none38.134.104.0/24No ROA covers it. Add a ROA for AS401322, maxLength 24.669 of 673
Route object: none38.134.104.0/24No route object for it. A route object for 38.134.104.0/23 with origin AS401322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401322 in the RIR database for the space.669 of 673
ROA: none38.134.105.0/24No ROA covers it. Add a ROA for AS401322, maxLength 24.669 of 673
Route object: none38.134.105.0/24No route object for it. A route object for 38.134.104.0/23 with origin AS401322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401322 in the RIR database for the space.669 of 673
ROA: none2602:f7cf::/48No ROA covers it. Add a ROA for AS401322, maxLength 48.635 of 636
Route object: none2602:f7cf::/48No route object for it. A route object for 2602:f7cf::/40 with origin AS401322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401322 in the RIR database for the space.635 of 636
ROA: none206.109.66.0/23No ROA covers it. Add a ROA for AS401322, maxLength 23.670 of 673
ROA: none206.109.82.0/24No ROA covers it. Add a ROA for AS401322, maxLength 24.670 of 673
ROA: none38.123.174.0/24No ROA covers it. Add a ROA for AS401322, maxLength 24.2 of 673
Route object: none189.13.1.0/24No route object for it. Add a route object with origin AS401322 in the RIR database for the space.673 of 673
Route object: none189.13.163.0/24No route object for it. Add a route object with origin AS401322 in the RIR database for the space.673 of 673
Route object: none189.13.248.0/24No route object for it. Add a route object with origin AS401322 in the RIR database for the space.673 of 673
Route object: none189.13.249.0/24No route object for it. Add a route object with origin AS401322 in the RIR database for the space.673 of 673
Route object: none189.13.250.0/24No route object for it. Add a route object with origin AS401322 in the RIR database for the space.673 of 673
Route object: none189.13.252.0/24No route object for it. Add a route object with origin AS401322 in the RIR database for the space.673 of 673
Route object: none189.13.253.0/24No route object for it. Add a route object with origin AS401322 in the RIR database for the space.673 of 673
Route object: none189.13.254.0/24No route object for it. Add a route object with origin AS401322 in the RIR database for the space.673 of 673
Route object: none189.13.255.0/24No route object for it. Add a route object with origin AS401322 in the RIR database for the space.673 of 673
Route object: none189.13.251.0/24No route object for it. Add a route object with origin AS401322 in the RIR database for the space.671 of 673
Route object: none189.13.50.0/24No route object for it. Add a route object with origin AS401322 in the RIR database for the space.667 of 673
Route object: RIR77.107.82.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
AS-SET: missing memberRADB::AS401322:AS-GLOBALAS401322:AS-GLOBAL (RADB) lists AS-EOIX; no IRR database read has it.
AS-SET: missing memberRADB::AS401322:AS-GLOBALAS401322:AS-GLOBAL (RADB) lists AS-IDCCUBE; no IRR database read has it.
AS-SET: missing memberRADB::AS401322:AS-GLOBALAS401322:AS-GLOBAL (RADB) lists AS199310:AS-QFNET; no IRR database read has it.
AS-SET: missing memberRADB::AS401322:AS-GLOBALAS401322:AS-GLOBAL (RADB) lists AS199436:AS-AUBREY; no IRR database read has it.
AS-SET: missing memberRADB::AS401322:AS-GLOBALAS401322:AS-GLOBAL (RADB) lists AS199436:AS-CUSTOMER-LAIN; no IRR database read has it.
AS-SET: missing memberRADB::AS401322:AS-GLOBALAS401322:AS-GLOBAL (RADB) lists AS215364:AS-KKC-NETWORK; no IRR database read has it.
AS-SET: missing memberRADB::AS401322:AS-GLOBALAS401322:AS-GLOBAL (RADB) lists AS215750:AS-SET; no IRR database read has it.
AS-SET: missing memberRADB::AS401322:AS-GLOBALAS401322:AS-GLOBAL (RADB) lists AS216324:AS-HN-NET; no IRR database read has it.

Route objects not announced

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

38.134.104.0/23ARINNo ROA
38.211.116.0/24ARINValid
50.2.205.0/24ARIN, RADBValid
90.96.81.0/24RADB, RIPEValid
164.37.235.0/24RADB, RIPEValid
189.13.100.0/24RADBNo ROA
191.222.243.0/24RIPEValid
192.78.219.0/24ARINInvalid: origin
212.134.132.0/24RADBValid
2602:f7cf::/40RADBNo ROA

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.