FRASER-CAPITAL

BGP inherited
Cluster stats
Netblocks9
Cluster ID210663782
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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

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
86.188.145.248/29 FRASER-CAPITAL RIPE ASSIGNED PA ● low
213.121.83.104/29 FRASER-CAPITAL RIPE ASSIGNED PA ● low
213.121.83.120/29 FRASER-CAPITAL RIPE ASSIGNED PA ● low
213.121.83.232/29 FRASER-CAPITAL RIPE ASSIGNED PA ● low
2a00:2381:3999::/48 FRASER-CAPITAL RIPE AGGREGATED-BY-LIR ● low
2a00:2381:3999:100::/56 FRASER-CAPITAL RIPE ASSIGNED ● low
2a00:2381:3999:300::/56 FRASER-CAPITAL RIPE ASSIGNED ● low
2a00:2381:3999:500::/56 FRASER-CAPITAL RIPE ASSIGNED ● low
2a00:2381:3999:d00::/56 FRASER-CAPITAL RIPE ASSIGNED ● low

Possibly related to this organisation

what's this?
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: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (9 of 9)
No discrepancies found among checked blocks.

NIC Handles

BTNET-MNT DUMY-RIPE DUMY-RIPE