JSMSR Network

Data as of 2026-08-16
BGP inherited
Cluster stats
Netblocks89 · 1,800 IPv4 addresses
IPv6 74 prefixes (largest 2602:f919::/40)
Registered in United States (13) · Canada (1) · United Kingdom (1) · Japan (1) · Taiwan (1)
Cluster ID222396907
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 27 shared RIR contact/maintainer handles
Registry names 29 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

8 weekly snapshots · JSON
92 +7 netblocks since 2026-07-05
2026-07-05 peak 92 2026-08-16

IP Ranges (89)

showing 50 of 89 — see all — ⬇ export CSV
CIDR Org name Registry Status Confidence
2.27.149.0/24 JSMSR Network BGP ANNOUNCED ● high
23.154.164.149/32 JSMSR Network PEERINGDB ASSIGNED ● high
23.162.24.0/24 JSMSR Network BGP ANNOUNCED ● high
23.177.40.0/24 JSMSR Network ARIN ASSIGNMENT ● high
33.0.0.69/32 JSMSR Network PEERINGDB ASSIGNED ● high
69.33.209.0/24 JSMSR Network BGP ANNOUNCED ● high
82.110.55.0/24 JSMSR Network BGP ANNOUNCED ● high
131.143.239.0/24 JSMSR Network ARIN ASSIGNMENT ● high
202.226.3.34/32 JSMSR Network PEERINGDB ASSIGNED ● high
203.163.223.63/32 JSMSR Network PEERINGDB ASSIGNED ● high
206.51.7.162/32 JSMSR Network PEERINGDB ASSIGNED ● high
206.81.104.98/32 JSMSR Network PEERINGDB ASSIGNED ● high
206.83.12.112/32 JSMSR Network PEERINGDB ASSIGNED ● high
206.83.136.87/32 JSMSR Network PEERINGDB ASSIGNED ● high
212.189.54.0/24 JSMSR Network BGP ANNOUNCED ● high
2001:504:1b:1::162/128 JSMSR Network PEERINGDB ASSIGNED ● high
2001:504:98::112/128 JSMSR Network PEERINGDB ASSIGNED ● high
2001:504:9e::87/128 JSMSR Network PEERINGDB ASSIGNED ● high
2402:b7c0:e000::1:2198:1/128 JSMSR Network PEERINGDB ASSIGNED ● high
2404:f4c0:f70e:1980::12:198/128 JSMSR Network PEERINGDB ASSIGNED ● high
2406:840:1f:1000:0:1:2198:1/128 JSMSR Network PEERINGDB ASSIGNED ● high
2406:840:1f:1000:0:1:2198:2/128 JSMSR Network PEERINGDB ASSIGNED ● high
2406:840:e180::/44 JSMSR Network BGP ANNOUNCED ● high
2406:840:e181::/48 JSMSR Network BGP ANNOUNCED ● high
2406:840:e182::/48 JSMSR Network BGP ANNOUNCED ● high
2406:d400:1:133:203:163:223:63/128 JSMSR Network PEERINGDB ASSIGNED ● high
2602:f429:31::5/128 JSMSR Network PEERINGDB ASSIGNED ● high
2602:f613::1219:8:1/128 JSMSR Network PEERINGDB ASSIGNED ● high
2602:f919::/40 JSMSR Network BGP ANNOUNCED ● high
2602:f919:40::/42 JSMSR Network BGP ANNOUNCED ● high
2602:f919:103::/48 JSMSR Network BGP ANNOUNCED ● high
2602:f919:104::/48 JSMSR Network BGP ANNOUNCED ● high
2602:f919:107::/48 JSMSR Network BGP ANNOUNCED ● high
2602:f919:108::/48 JSMSR Network BGP ANNOUNCED ● high
2602:f919:10a::/48 JSMSR Network BGP ANNOUNCED ● high
2602:f919:10b::/48 JSMSR Network BGP ANNOUNCED ● high
2602:f919:10c::/48 JSMSR Network BGP ANNOUNCED ● high
2602:f919:90f:fffa::1219:8/128 JSMSR Network PEERINGDB ASSIGNED ● high
2602:f919:920::/48 JSMSR Network BGP ANNOUNCED ● high
2602:f919:921::/48 JSMSR Network BGP ANNOUNCED ● high
2602:f919:925::/48 JSMSR Network BGP ANNOUNCED ● high
2602:f919:926::/48 JSMSR Network BGP ANNOUNCED ● high
2602:f919:931::/48 JSMSR Network BGP ANNOUNCED ● high
2602:f919:932::/48 JSMSR Network BGP ANNOUNCED ● high
2602:f919:934::/48 JSMSR Network BGP ANNOUNCED ● high
2602:f919:935::/48 JSMSR Network BGP ANNOUNCED ● high
2602:f919:936::/48 JSMSR Network BGP ANNOUNCED ● high
2602:f919:939::/48 JSMSR Network BGP ANNOUNCED ● high
2602:f919:93d::/48 JSMSR Network BGP ANNOUNCED ● high
2602:f919:93e::/48 JSMSR Network BGP ANNOUNCED ● high

IPv6 ranges (74)

showing the 15 largest allocations
CIDR
2602:f919::/40
2a0a:6040:7e00::/40
2a0f:1cc5:3600::/40
2602:f919:40::/42
2406:840:e180::/44
2a0a:6040:7e10::/44
2a0a:6040:7e20::/44
2a0a:6040:7e30::/44
2a12:3fc2:e710::/44
2a12:3fc2:e720::/44
2a12:3fc2:e7f0::/44
2406:840:e181::/48
2406:840:e182::/48
2406:840:e183::/48
2406:840:e184::/48

Network trust

what's this?
RPKI hygiene: B how networks compare →
85.9% of checked blocks have valid RPKI ROA coverage (79 of 92)
Possible discrepancies (25)

These blocks are registered to JSMSR Network but cryptographically authorized for a different, unrelated network (3 distinct holders) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2a0a:6040:7e00::/40 /40 authorized for AS134478 — Eang Kong (Cambodia) Co., Ltd
2a0a:6040:7e10::/44 /44 authorized for AS134478 — Eang Kong (Cambodia) Co., Ltd
2a0a:6040:7e20::/44 /44 authorized for AS134478 — Eang Kong (Cambodia) Co., Ltd
2a0a:6040:7e30::/44 /44 authorized for AS134478 — Eang Kong (Cambodia) Co., Ltd
2a0a:6040:7e10::/48 /48 authorized for AS134478 — Eang Kong (Cambodia) Co., Ltd
2a0a:6040:7e11::/48 /48 authorized for AS134478 — Eang Kong (Cambodia) Co., Ltd
2a0a:6040:7e12::/48 /48 authorized for AS134478 — Eang Kong (Cambodia) Co., Ltd
2a0a:6040:7e21::/48 /48 authorized for AS134478 — Eang Kong (Cambodia) Co., Ltd
2a0a:6040:7e22::/48 /48 authorized for AS134478 — Eang Kong (Cambodia) Co., Ltd
2a0a:6040:7e26::/48 /48 authorized for AS134478 — Eang Kong (Cambodia) Co., Ltd
2a0a:6040:7e23::/48 /48 authorized for AS134478 — Eang Kong (Cambodia) Co., Ltd
2a0a:6040:7e24::/48 /48 authorized for AS134478 — Eang Kong (Cambodia) Co., Ltd
2a0a:6040:7e31::/48 /48 authorized for AS134478 — Eang Kong (Cambodia) Co., Ltd
2a0a:6040:7e33::/48 /48 authorized for AS134478 — Eang Kong (Cambodia) Co., Ltd
2a0a:6040:7e13::/48 /48 authorized for AS134478 — Eang Kong (Cambodia) Co., Ltd
+10 more — see the REST API

NIC Handles

AJ490-AP AS12198 AS12198 AS401009 AS9304 C10892645 C11429503 CLOUDIE-MNT DUMY-RIPE DUMY-RIPE JNL-41 JSMSR-ARIN +15 more