Glecom
Cluster stats
Netblocks14
All fragments 16 blocks across 2 clusters
Cluster ID193383113
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

Footprint over time

2 weekly snapshots · JSON
14 0 netblocks since 2026-07-05
2026-07-05 peak 14 2026-07-06

IP Ranges (14)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.1.215.26/32 Glecom PEERINGDB ASSIGNED ● high
192.121.80.39/32 Glecom PEERINGDB ASSIGNED ● high
193.110.12.178/32 Glecom PEERINGDB ASSIGNED ● high
193.110.13.178/32 Glecom PEERINGDB ASSIGNED ● high
193.243.183.139/32 Glecom PEERINGDB ASSIGNED ● high
194.68.123.165/32 Glecom PEERINGDB ASSIGNED ● high
194.68.128.165/32 Glecom PEERINGDB ASSIGNED ● high
2001:7f8:d:fe::165/128 Glecom PEERINGDB ASSIGNED ● high
2001:7f8:d:ff::165/128 Glecom PEERINGDB ASSIGNED ● high
2001:7f8:21:9::178/128 Glecom PEERINGDB ASSIGNED ● high
2001:7f8:21:10::178/128 Glecom PEERINGDB ASSIGNED ● high
2001:7f8:3e:0:a500:5:2177:1/128 Glecom PEERINGDB ASSIGNED ● high
2001:7f8:117::5:2177:1/128 Glecom PEERINGDB ASSIGNED ● high
2001:7f8:153::5:2177:1/128 Glecom PEERINGDB ASSIGNED ● high

Network trust

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

NIC Handles

AS52177