SPITFIRE_EFM_POINTTOPOINT
Unresolved
Cluster stats
Netblocks8
All fragments 16 blocks across 2 clusters
Cluster ID192407235
RegistryRIPE
Customersfind 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
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-06

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.24.2.0/23 SPITFIRE_EFM_POINTTOPOINT RIPE ASSIGNED PA ● low
31.24.4.0/23 SPITFIRE_EFM_POINTTOPOINT RIPE ASSIGNED PA ● low
31.24.6.0/23 SPITFIRE_EFM_POINTTOPOINT RIPE ASSIGNED PA ● low
87.224.37.208/28 SPITFIRE_EFM_POINTTOPOINT RIPE ASSIGNED PA ● low
109.238.64.0/23 SPITFIRE_EFM_POINTTOPOINT RIPE ASSIGNED PA ● low
109.238.78.0/23 SPITFIRE_EFM_POINTTOPOINT RIPE ASSIGNED PA ● low
185.15.104.0/23 SPITFIRE_EFM_POINTTOPOINT RIPE ASSIGNED PA ● low
185.15.106.0/23 SPITFIRE_EFM_POINTTOPOINT 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 (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE SPITFIRE-UK-MNT