JS-TELECOM

Data as of 2026-09-20
BGP inherited
This organisation
Netblocks11
Also registered under this name 14 netblocks across 3 separate records
Record ID242169903
RegistryAPNIC
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 14 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
61.130.68.32/30 JS-TELECOM APNIC ASSIGNED NON-PORTABLE ● high
61.130.68.48/30 JS-TELECOM APNIC ASSIGNED NON-PORTABLE ● high
61.130.68.56/30 JS-TELECOM APNIC ASSIGNED NON-PORTABLE ● high
61.130.68.64/30 JS-TELECOM APNIC ASSIGNED NON-PORTABLE ● high
61.130.68.76/30 JS-TELECOM APNIC ASSIGNED NON-PORTABLE ● high
61.130.68.232/30 JS-TELECOM APNIC ASSIGNED NON-PORTABLE ● high
61.130.68.240/30 JS-TELECOM APNIC ASSIGNED NON-PORTABLE ● high
122.227.81.116/30 JS-TELECOM APNIC ASSIGNED NON-PORTABLE ● high
122.227.81.120/30 JS-TELECOM APNIC ASSIGNED NON-PORTABLE ● high
218.72.255.212/30 JS-TELECOM APNIC ASSIGNED NON-PORTABLE ● high
218.72.255.244/30 JS-TELECOM APNIC ASSIGNED NON-PORTABLE ● high

Footprint over time

13 weekly snapshots · JSON
11 0 netblocks since 2026-07-05
2026-07-05 peak 11 2026-09-20

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (11 of 11)
No discrepancies found among checked blocks.

NIC Handles

AC1602-AP CQ11-AP LY3827-AP LY3828-AP LY3836-AP LY3839-AP LY3840-AP LY3851-AP LY3852-AP LY3854-AP LY3864-AP LY3881-AP +2 more