ORBE TELECOM
Cluster stats
Netblocks17
Cluster ID191585777
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 (17)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.72.110/32 ORBE TELECOM PEERINGDB ASSIGNED ● high
45.68.73.19/32 ORBE TELECOM PEERINGDB ASSIGNED ● high
45.68.81.104/32 ORBE TELECOM PEERINGDB ASSIGNED ● high
167.249.16.0/22 ORBE TELECOM BGP ANNOUNCED ● high
167.249.16.0/23 ORBE TELECOM BGP ANNOUNCED ● high
167.249.18.0/23 ORBE TELECOM BGP ANNOUNCED ● high
187.16.218.32/32 ORBE TELECOM PEERINGDB ASSIGNED ● high
187.16.222.124/32 ORBE TELECOM PEERINGDB ASSIGNED ● high
2001:12f8::218:32/128 ORBE TELECOM PEERINGDB ASSIGNED ● high
2001:12f8::222:124/128 ORBE TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:2::53:104/128 ORBE TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:9::110/128 ORBE TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:9::145:19/128 ORBE TELECOM PEERINGDB ASSIGNED ● high
2804:2b88::/33 ORBE TELECOM BGP ANNOUNCED ● high
2804:2b88::/32 ORBE TELECOM BGP ANNOUNCED ● high
2804:2b88:8000::/33 ORBE TELECOM BGP ANNOUNCED ● high
2804:2b88::/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 (17 of 17)
No discrepancies found among checked blocks.

NIC Handles

AS265158 AS265158