bgpreport

Network · data from 2026-11-12

AS63701 JSMNET - Jishi Media Co ., Ltd.

Registry name: JSMNET - Jishi Media Co ., Ltd., CN · not in PeeringDB

11IPv4 routes 100.0% RPKI valid · 36.4% with a route object
1IPv6 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
7Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS63701, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS63701, 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.
103.57.12.0/23 Valid Nonecovered by 103.57.12.0/22 672 100% 67
103.75.104.0/22 Valid None 57 8%low visibility 33
103.75.107.0/24 Valid None 57 8%low visibility 33
103.88.96.0/22 Valid None 57 8%low visibility 33
103.125.236.0/22 Valid None 57 8%low visibility 33
103.152.209.0/24 Valid None 57 8%low visibility 33
218.246.48.0/22 Valid None 57 8%low visibility 33
2407:4980::/32 Valid None 43 7%low visibility 30
45.116.208.0/22 Valid Other IRR onlyRADB 673 100% 67
45.123.128.0/22 Valid Other IRR onlyRADB 673 100% 67
103.57.12.0/22 Valid Other IRR onlyRADB 673 100% 67
103.63.244.0/22 Valid Other IRR onlyRADB 673 100% 67

AS-SET

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

  • Route object: none8
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
Route object: none103.57.12.0/23No route object for it. A route object for 103.57.12.0/22 with origin AS63701 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63701 in the RIR database for the space.672 of 673
Route object: none103.75.104.0/22No route object for it. Add a route object with origin AS63701 in the RIR database for the space.57 of 673
Route object: none103.75.107.0/24No route object for it. Add a route object with origin AS63701 in the RIR database for the space.57 of 673
Route object: none103.88.96.0/22No route object for it. Add a route object with origin AS63701 in the RIR database for the space.57 of 673
Route object: none103.125.236.0/22No route object for it. Add a route object with origin AS63701 in the RIR database for the space.57 of 673
Route object: none103.152.209.0/24No route object for it. Add a route object with origin AS63701 in the RIR database for the space.57 of 673
Route object: none218.246.48.0/22No route object for it. Add a route object with origin AS63701 in the RIR database for the space.57 of 673
Route object: none2407:4980::/32No route object for it. Add a route object with origin AS63701 in the RIR database for the space.43 of 636
Route object: RIR45.116.208.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR45.123.128.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.57.12.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.63.244.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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