KOM i TEX
Cluster stats
Netblocks12
All fragments 13 blocks across 2 clusters
Cluster ID193384815
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
12 0 netblocks since 2026-07-05
2026-07-05 peak 12 2026-07-06

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
178.18.230.37/32 KOM i TEX PEERINGDB ASSIGNED ● high
185.0.42.65/32 KOM i TEX PEERINGDB ASSIGNED ● high
185.1.63.18/32 KOM i TEX PEERINGDB ASSIGNED ● high
185.1.134.4/32 KOM i TEX PEERINGDB ASSIGNED ● high
185.1.213.107/32 KOM i TEX PEERINGDB ASSIGNED ● high
185.1.225.30/32 KOM i TEX PEERINGDB ASSIGNED ● high
193.25.181.48/32 KOM i TEX PEERINGDB ASSIGNED ● high
2001:7f8:6c::273/128 KOM i TEX PEERINGDB ASSIGNED ● high
2001:7f8:d8::4/128 KOM i TEX PEERINGDB ASSIGNED ● high
2001:7f8:115:1::65/128 KOM i TEX PEERINGDB ASSIGNED ● high
2001:7f8:14d::107/128 KOM i TEX PEERINGDB ASSIGNED ● high
2a03:5f80:7::230:37/128 KOM i TEX PEERINGDB ASSIGNED ● high

Network trust

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

NIC Handles

AS30886