bgpreport

Network · data from 2026-11-12

AS140096 Jinx

Registry name: JINX-AS-AP - JINX CO., LIMITED, HK · PeeringDB

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

Announced routes

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

2401:d9c0:2000::/36 No ROA Other IRR onlyRADB 634 100% 67
2401:d9c0:2000::/44 No ROA Other IRR onlyRADB 634 100% 67
2401:d9c0:2010::/44 No ROA Other IRR onlyRADB 634 100% 67
199.15.76.0/23 Valid Other IRR onlyRADB 672 100% 67
199.15.78.0/23 Valid Other IRR onlyRADB 672 100% 67
2604:d6c0::/32 Valid Other IRR onlyRADB 635 100% 70
199.15.76.0/24 Valid Other IRR onlyRADB 399 59% 65
199.15.77.0/24 Valid Other IRR onlyRADB 399 59% 65
199.15.78.0/24 Valid Other IRR onlyRADB 399 59% 65
199.15.79.0/24 Valid Other IRR onlyRADB 399 59% 65
124.108.20.0/24 Valid RIR databaseAPNIC 673 100% 67
182.255.32.0/22 Valid RIR databaseAPNIC, RADB 673 100% 67
182.255.33.0/24 Valid RIR databaseAPNIC 673 100% 67
182.255.35.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.169.217.0/24 Valid RIR databaseAPNIC 672 100% 67
161.129.46.0/24 Valid RIR databaseARIN, RADB 671 100% 67
161.129.42.0/24 Valid RIR databaseARIN, RADB 670 100% 67
2400:cca0:2101::/48 Valid RIR databaseAPNIC 636 100% 67
103.55.5.0/24 Valid RIR databaseAPNIC, RADB 160 24% 55
182.255.32.0/24 Valid RIR databaseAPNIC 160 24% 55

AS-SET

PeeringDB's irr_as_set for AS140096: AS140096:AS-JINX. 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 (AS140096 isn't in the set, or no route object for AS140096 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 objectsAS140096 in itNot covered
AS140096:AS-JINX RADBlists itself further down6 member sets in no database: AS-ARESFLARE-TRANSIT, AS-IQ-TW, AS-JHL, AS15143:AS-SET, AS38566:AS-THNTTCTNET … 1,603178198,291 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 51 are in fix.csv.

  • ROA: none3
  • Route object: RIR10
  • AS-SET: missing member6
  • Route object: not announced32
ChangePrefix or setDetailFull-table peers
ROA: none2401:d9c0:2000::/36No ROA covers it. Add a ROA for AS140096, maxLength 36.634 of 636
Route object: RIR2401:d9c0:2000::/36Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2401:d9c0:2000::/44No ROA covers it. Add a ROA for AS140096, maxLength 44.634 of 636
Route object: RIR2401:d9c0:2000::/44Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2401:d9c0:2010::/44No ROA covers it. Add a ROA for AS140096, maxLength 44.634 of 636
Route object: RIR2401:d9c0:2010::/44Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR199.15.76.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR199.15.78.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2604:d6c0::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR199.15.76.0/24Route object only in RADB. Add it in the RIR database for the space.399 of 673
Route object: RIR199.15.77.0/24Route object only in RADB. Add it in the RIR database for the space.399 of 673
Route object: RIR199.15.78.0/24Route object only in RADB. Add it in the RIR database for the space.399 of 673
Route object: RIR199.15.79.0/24Route object only in RADB. Add it in the RIR database for the space.399 of 673
AS-SET: missing memberAS140096:AS-JINXAS140096:AS-JINX (RADB) lists AS-ARESFLARE-TRANSIT; no IRR database read has it.
AS-SET: missing memberAS140096:AS-JINXAS140096:AS-JINX (RADB) lists AS-IQ-TW; no IRR database read has it.
AS-SET: missing memberAS140096:AS-JINXAS140096:AS-JINX (RADB) lists AS-JHL; no IRR database read has it.
AS-SET: missing memberAS140096:AS-JINXAS140096:AS-JINX (RADB) lists AS15143:AS-SET; no IRR database read has it.
AS-SET: missing memberAS140096:AS-JINXAS140096:AS-JINX (RADB) lists AS38566:AS-THNTTCTNET; no IRR database read has it.
AS-SET: missing memberAS140096:AS-JINXAS140096:AS-JINX (RADB) lists AS401984:AS-SET; no IRR database read has it.

Route objects not announced

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

38.6.224.0/22RADBNo ROA
38.6.224.0/23RADBNo ROA
38.6.226.0/23RADBNo ROA
38.47.192.0/18ARINValid
38.181.0.0/18ARINValid
103.5.54.0/23RADBNo ROA
103.55.4.0/23APNIC, RADBValid
103.55.4.0/24APNIC, RADBValid
103.116.72.0/22APNIC, RADBValid
103.116.72.0/23APNICValid
103.116.72.0/24APNICValid
103.116.73.0/24APNICValid
103.116.74.0/23APNICValid
103.116.74.0/24APNICValid
103.116.75.0/24APNICValid
103.169.216.0/23RADBNo ROA
103.169.216.0/24APNIC, RADBValid
103.200.112.0/23APNIC, RADBValid
103.200.112.0/24APNIC, RADBValid
103.200.113.0/24APNIC, RADBValid
124.108.20.0/23APNIC, RADBValid
124.108.21.0/24APNIC, RADBValid
161.129.43.0/24ARIN, RADBValid
177.0.134.0/24APNICValid
182.255.32.0/23APNICValid
182.255.34.0/23APNICValid
182.255.34.0/24APNICValid
198.176.55.0/24ARINValid
198.176.58.0/24ARINValid
199.15.76.0/22RADBValid
2604:d6c0::/48RADBValid
2a0f:7802:f000::/44RADBNo 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.