bgpreport

Network · data from 2026-11-12

AS23841 TJBTN - 6/F, No.3 Huatian Road, New Technology Industry Area

Registry name: TJBTN - 6/F, No.3 Huatian Road, New Technology Industry Area, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS23841, 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.
111.31.196.0/24 Valid None 672 100% 67
111.31.239.0/24 Valid None 672 100% 67
240a:4088:a000::/35 Valid None 69 11% 34
240a:4090:a000::/35 Valid None 69 11% 34
240a:420a::/31 Valid None 69 11% 34
103.1.20.0/22 Valid None 57 8%low visibility 33
221.129.0.0/16 Valid None 57 8%low visibility 33
2401:ca00::/32 Valid None 43 7%low visibility 30
211.148.160.0/19 Valid Other IRR onlyNTTCOM, RADB 84 12% 37

AS-SET

AS23841 isn't in PeeringDB, where networks name their AS-SET.

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

  • Route object: none8
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
Route object: none111.31.196.0/24No route object for it. Add a route object with origin AS23841 in the RIR database for the space.672 of 673
Route object: none111.31.239.0/24No route object for it. Add a route object with origin AS23841 in the RIR database for the space.672 of 673
Route object: none240a:4088:a000::/35No route object for it. Add a route object with origin AS23841 in the RIR database for the space.69 of 636
Route object: none240a:4090:a000::/35No route object for it. Add a route object with origin AS23841 in the RIR database for the space.69 of 636
Route object: none240a:420a::/31No route object for it. Add a route object with origin AS23841 in the RIR database for the space.69 of 636
Route object: none103.1.20.0/22No route object for it. Add a route object with origin AS23841 in the RIR database for the space.57 of 673
Route object: none221.129.0.0/16No route object for it. Add a route object with origin AS23841 in the RIR database for the space.57 of 673
Route object: none2401:ca00::/32No route object for it. Add a route object with origin AS23841 in the RIR database for the space.43 of 636
Route object: RIR211.148.160.0/19Route object only in NTTCOM, RADB. Add it in the RIR database for the space.84 of 673

Route objects not announced

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