F2X Operator B.V.
Cluster stats
| Netblocks | 15 |
| Cluster ID | 193387089 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (15)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 80.249.210.110/32 | F2X Operator B.V. | PEERINGDB | ASSIGNED | ● high |
| 185.1.112.109/32 | F2X Operator B.V. | PEERINGDB | ASSIGNED | ● high |
| 185.1.112.110/32 | F2X Operator B.V. | PEERINGDB | ASSIGNED | ● high |
| 185.1.160.157/32 | F2X Operator B.V. | PEERINGDB | ASSIGNED | ● high |
| 185.1.184.96/32 | F2X Operator B.V. | PEERINGDB | ASSIGNED | ● high |
| 185.1.222.46/32 | F2X Operator B.V. | PEERINGDB | ASSIGNED | ● high |
| 193.239.118.182/32 | F2X Operator B.V. | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1::a505:7112:1/128 | F2X Operator B.V. | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:13::a505:7112:1/128 | F2X Operator B.V. | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:83::5:7112:1/128 | F2X Operator B.V. | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:83::5:7112:2/128 | F2X Operator B.V. | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:b7::a505:7112:1/128 | F2X Operator B.V. | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:10f::df18:157/128 | F2X Operator B.V. | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:134::96/128 | F2X Operator B.V. | PEERINGDB | ASSIGNED | ● high |
| 79.244.198.216/29 | F2X-OPERATOR-ERDING-NET | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
73.3%
of checked blocks have valid RPKI ROA coverage
(11 of 15)
No discrepancies found among checked blocks.
NIC Handles
AS57112
DTAG-NIC
DUMY-RIPE
DUMY-RIPE