FULCRUM

BGP inherited
Cluster stats
Netblocks9 · 357 IPv4 addresses
Registered in United Kingdom (5) · Spain (4)
All fragments 20 blocks across 9 clusters
Cluster ID209415215
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.255.138.0/24 FULCRUM RIPE ASSIGNED PA ● low
62.99.69.200/29 FULCRUM RIPE ASSIGNED PA ● low
62.99.78.102/32 FULCRUM RIPE ASSIGNED PA ● low
62.99.78.223/32 FULCRUM RIPE ASSIGNED PA ● low
62.99.80.76/30 FULCRUM RIPE ASSIGNED PA ● low
83.244.144.208/28 FULCRUM RIPE ASSIGNED PA ● low
83.244.146.240/28 FULCRUM RIPE ASSIGNED PA ● low
83.244.147.128/27 FULCRUM RIPE ASSIGNED PA ● low
83.244.225.32/27 FULCRUM RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “FULCRUM” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

what's this?
RPKI hygiene: B how networks compare →
88.9% of checked blocks have valid RPKI ROA coverage (8 of 9)
No discrepancies found among checked blocks.

NIC Handles

AS31137-MNT DUMY-RIPE DUMY-RIPE EUSKALTEL-MNT EXPONENTIAL-E-MNT