R3 TELECOM
Cluster stats
Netblocks16
All fragments 48 blocks across 5 clusters
Cluster ID191589560
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 2 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (16)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.73.48/32 R3 TELECOM PEERINGDB ASSIGNED ● high
45.227.1.2/32 R3 TELECOM PEERINGDB ASSIGNED ● high
177.37.16.0/22 R3 TELECOM BGP ANNOUNCED ● high
177.37.16.0/23 R3 TELECOM BGP ANNOUNCED ● high
177.37.18.0/23 R3 TELECOM BGP ANNOUNCED ● high
177.37.18.0/24 R3 TELECOM BGP ANNOUNCED ● high
187.16.218.135/32 R3 TELECOM PEERINGDB ASSIGNED ● high
200.219.147.57/32 R3 TELECOM PEERINGDB ASSIGNED ● high
2001:12f8::218:135/128 R3 TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:9::145:48/128 R3 TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:10::57/128 R3 TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:31::2/128 R3 TELECOM PEERINGDB ASSIGNED ● high
2804:6e94::/33 R3 TELECOM BGP ANNOUNCED ● high
2804:6e94::/32 R3 TELECOM BGP ANNOUNCED ● high
2804:6e94:8000::/33 R3 TELECOM BGP ANNOUNCED ● high
2804:6e94::/32 UNKNOWN LACNIC allocated ● medium

Network trust

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

NIC Handles

AS270606 AS270606