Fortex-Telecom
Cluster stats
Netblocks12
All fragments 48 blocks across 5 clusters
Cluster ID193382224
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 (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.28.19.139/32 Fortex-Telecom PEERINGDB ASSIGNED ● high
37.9.49.168/32 Fortex-Telecom PEERINGDB ASSIGNED ● high
178.18.226.128/32 Fortex-Telecom PEERINGDB ASSIGNED ● high
185.1.152.30/32 Fortex-Telecom PEERINGDB ASSIGNED ● high
185.232.60.128/32 Fortex-Telecom PEERINGDB ASSIGNED ● high
193.27.37.161/32 Fortex-Telecom PEERINGDB ASSIGNED ● high
193.106.112.218/32 Fortex-Telecom PEERINGDB ASSIGNED ● high
195.208.209.61/32 Fortex-Telecom PEERINGDB ASSIGNED ● high
2001:7f8:20:101::209:61/128 Fortex-Telecom PEERINGDB ASSIGNED ● high
2a00:13c0:3:1::1f1c:138b/128 Fortex-Telecom PEERINGDB ASSIGNED ● high
2a03:5f80:4::226:128/128 Fortex-Telecom PEERINGDB ASSIGNED ● high
2a0d:e180::60:128/128 Fortex-Telecom PEERINGDB ASSIGNED ● high

Network trust

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

NIC Handles

AS48166