F Tnet
FTNET
Cluster stats
| Netblocks | 4 |
| All fragments | 15 blocks across 2 clusters |
| Cluster ID | 192922814 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 11 shared RIR contact/maintainer handles |
| Registry names | 4 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 89.16.96.128/28 | FTNET | RIPE | ASSIGNED PA | ● low |
| 119.226.140.44 – 119.226.140.127 | FTNET | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 211.153.47.0 – 211.153.48.255 | FTnet | APNIC | assigned non-portable | ● low |
| 2a02:e90:2000::/48 | FTNET-IPv6-NET | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
75.0%
of checked blocks have valid RPKI ROA coverage
(3 of 4)
Possible discrepancies (2)
These blocks are registered to F Tnet but cryptographically authorized for a different, unrelated network (2 distinct holders) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2a02:e90:2000::/48 /48 | authorized for AS15389 — P/F Telefonverkid |
| 211.153.47.0 – 211.153.48.255 /23 | authorized for AS4847 — China Networks Inter-Exchange |
NIC Handles
DUMY-RIPE
DUMY-RIPE
FT-NET-MNT
HM66-AP
HS51-AP
HS51-AP
KF31-AP
KTTKNET-MNT
MAINT-BJENET-CNNIC-AP
MAINT-IN-IRINN
MAINT-IN-SIFY