Fortex-Telecom
Data as of 2026-08-23
Handle
Cluster stats
| Netblocks | 12 |
| IPv6 | 4 prefixes (largest 2001:7f8:20:101::209:61/128) |
| Registered in | Russia (6) · AG (1) |
| Cluster ID | 229183541 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| 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 · report an issue | |
Footprint over time
9 weekly snapshots · JSON
12
0 netblocks since 2026-07-05
2026-07-05
peak 12
2026-08-23
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 |
IPv6 ranges (4)
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