bgpreport

Network · data from 2026-11-12

AS394869 APNC

Registry name: APNC - Asia Pacific Network Corporation, US · PeeringDB

19IPv4 routes 21.1% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
15No 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 AS394869, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS394869, 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.84.162.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.84.165.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.102.225.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
38.102.242.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.105.22.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.107.168.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.107.174.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.107.183.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.146.161.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.105.20.0/24 No ROA Other IRR onlyRADB 671 100% 67
38.105.21.0/24 No ROA Other IRR onlyRADB 671 100% 67
38.107.171.0/24 No ROA Other IRR onlyRADB 671 100% 67
38.107.176.0/24 No ROA Other IRR onlyRADB 671 100% 67
38.95.230.0/24 No ROA Other IRR onlyRADB 670 100% 67
38.105.19.0/24 No ROA Other IRR onlyRADB 670 100% 67
49.157.63.0/24 Valid RIR databaseAPNIC 672 100% 67
112.199.92.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
61.245.31.0/24 Valid RIR databaseAPNIC 671 100% 67
115.84.249.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67

AS-SET

PeeringDB's irr_as_set for AS394869: AS394869:AS-CONE. 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 (AS394869 isn't in the set, or no route object for AS394869 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 objectsAS394869 in itNot covered
AS394869:AS-CONE RADB 1119 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 30 are in fix.csv.

  • ROA: none15
  • Route object: RIR15
ChangePrefix or setDetailFull-table peers
ROA: none38.84.162.0/24No ROA covers it. Add a ROA for AS394869, maxLength 24.672 of 673
Route object: RIR38.84.162.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.84.165.0/24No ROA covers it. Add a ROA for AS394869, maxLength 24.672 of 673
Route object: RIR38.84.165.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.102.225.0/24No ROA covers it. Add a ROA for AS394869, maxLength 24.672 of 673
Route object: RIR38.102.225.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.102.242.0/24No ROA covers it. Add a ROA for AS394869, maxLength 24.672 of 673
Route object: RIR38.102.242.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.105.22.0/24No ROA covers it. Add a ROA for AS394869, maxLength 24.672 of 673
Route object: RIR38.105.22.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.107.168.0/24No ROA covers it. Add a ROA for AS394869, maxLength 24.672 of 673
Route object: RIR38.107.168.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.107.174.0/24No ROA covers it. Add a ROA for AS394869, maxLength 24.672 of 673
Route object: RIR38.107.174.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.107.183.0/24No ROA covers it. Add a ROA for AS394869, maxLength 24.672 of 673
Route object: RIR38.107.183.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.146.161.0/24No ROA covers it. Add a ROA for AS394869, maxLength 24.672 of 673
Route object: RIR38.146.161.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.105.20.0/24No ROA covers it. Add a ROA for AS394869, maxLength 24.671 of 673
Route object: RIR38.105.20.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.105.21.0/24No ROA covers it. Add a ROA for AS394869, maxLength 24.671 of 673
Route object: RIR38.105.21.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.107.171.0/24No ROA covers it. Add a ROA for AS394869, maxLength 24.671 of 673
Route object: RIR38.107.171.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.107.176.0/24No ROA covers it. Add a ROA for AS394869, maxLength 24.671 of 673
Route object: RIR38.107.176.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.95.230.0/24No ROA covers it. Add a ROA for AS394869, maxLength 24.670 of 673
Route object: RIR38.95.230.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.105.19.0/24No ROA covers it. Add a ROA for AS394869, maxLength 24.670 of 673
Route object: RIR38.105.19.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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