Jupiter Telecom
Cluster stats
Netblocks14
All fragments 258 blocks across 29 clusters
Cluster ID193383045
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 (14)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.72.149/32 Jupiter Telecom PEERINGDB ASSIGNED ● high
45.68.72.186/32 Jupiter Telecom PEERINGDB ASSIGNED ● high
45.184.144.88/32 Jupiter Telecom PEERINGDB ASSIGNED ● high
187.16.195.24/32 Jupiter Telecom PEERINGDB ASSIGNED ● high
187.16.213.109/32 Jupiter Telecom PEERINGDB ASSIGNED ● high
187.16.220.75/32 Jupiter Telecom PEERINGDB ASSIGNED ● high
187.16.221.45/32 Jupiter Telecom PEERINGDB ASSIGNED ● high
2001:12f8::213:109/128 Jupiter Telecom PEERINGDB ASSIGNED ● high
2001:12f8::220:75/128 Jupiter Telecom PEERINGDB ASSIGNED ● high
2001:12f8::221:45/128 Jupiter Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:9::149/128 Jupiter Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:9::186/128 Jupiter Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:13::88/128 Jupiter Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:18::24/128 Jupiter Telecom PEERINGDB ASSIGNED ● high

Network trust

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

NIC Handles

AS28191