JSX TELECOM
Cluster stats
Netblocks12
Cluster ID193382719
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.75.21/32 JSX TELECOM PEERINGDB ASSIGNED ● high
45.68.80.44/32 JSX TELECOM PEERINGDB ASSIGNED ● high
64.191.232.21/32 JSX TELECOM PEERINGDB ASSIGNED ● high
187.16.215.62/32 JSX TELECOM PEERINGDB ASSIGNED ● high
187.16.221.172/32 JSX TELECOM PEERINGDB ASSIGNED ● high
200.219.145.54/32 JSX TELECOM PEERINGDB ASSIGNED ● high
2001:504:0:7::15/128 JSX TELECOM PEERINGDB ASSIGNED ● high
2001:12f8::215:62/128 JSX TELECOM PEERINGDB ASSIGNED ● high
2001:12f8::221:172/128 JSX TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:2::44/128 JSX TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:8::54/128 JSX TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:9::147:21/128 JSX TELECOM PEERINGDB ASSIGNED ● high

Network trust

what's this?
RPKI hygiene: B how networks compare →
83.3% of checked blocks have valid RPKI ROA coverage (10 of 12)
No discrepancies found among checked blocks.

NIC Handles

AS52696