FF3396-AMSTERDAM
Cluster stats
| Netblocks | 17 |
| All fragments | 24 blocks across 6 clusters |
| Cluster ID | 192376331 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
17
0 netblocks since 2026-07-05
2026-07-05
peak 17
2026-07-06
IP Ranges (17)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 31.223.163.240/29 | FF3396-AMSTERDAM | RIPE | ASSIGNED PA | ● low |
| 37.17.209.48/29 | FF3396-AMSTERDAM | RIPE | ASSIGNED PA | ● low |
| 37.17.209.160/27 | FF3396-AMSTERDAM | RIPE | ASSIGNED PA | ● low |
| 37.17.212.216/29 | FF3396-AMSTERDAM | RIPE | ASSIGNED PA | ● low |
| 37.17.216.64/26 | FF3396-AMSTERDAM | RIPE | ASSIGNED PA | ● low |
| 37.17.216.192/29 | FF3396-AMSTERDAM | RIPE | ASSIGNED PA | ● low |
| 80.246.195.48/29 | FF3396-AMSTERDAM | RIPE | ASSIGNED PA | ● low |
| 80.255.252.224/29 | FF3396-AMSTERDAM | RIPE | ASSIGNED PA | ● low |
| 81.21.138.0/29 | FF3396-AMSTERDAM | RIPE | ASSIGNED PA | ● low |
| 81.21.140.104/29 | FF3396-AMSTERDAM | RIPE | ASSIGNED PA | ● low |
| 81.30.42.0/26 | FF3396-AMSTERDAM | RIPE | ASSIGNED PA | ● low |
| 171.33.129.160/27 | FF3396-AMSTERDAM | RIPE | ASSIGNED PA | ● low |
| 176.74.230.48/29 | FF3396-AMSTERDAM | RIPE | ASSIGNED PA | ● low |
| 176.74.242.0/27 | FF3396-AMSTERDAM | RIPE | ASSIGNED PA | ● low |
| 176.74.253.0/28 | FF3396-AMSTERDAM | RIPE | ASSIGNED PA | ● low |
| 176.74.253.32/29 | FF3396-AMSTERDAM | RIPE | ASSIGNED PA | ● low |
| 176.74.253.136/29 | FF3396-AMSTERDAM | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(17 of 17)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
SIGNET-MNT