FIMASRL

BGP inherited
Cluster stats
Netblocks9
Cluster ID209074526
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 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
80.22.108.164/30 FIMASRL RIPE ASSIGNED PA ● low
81.123.248.96/29 FIMASRL RIPE ASSIGNED PA ● low
85.33.108.232/29 FIMASRL RIPE ASSIGNED PA ● low
85.41.107.224/29 FIMASRL RIPE ASSIGNED PA ● low
85.46.191.184/29 FIMASRL RIPE ASSIGNED PA ● low
94.88.144.88/29 FIMASRL RIPE ASSIGNED PA ● low
195.120.4.228/30 FIMASRL RIPE ASSIGNED PA ● low
212.131.12.240/29 FIMASRL RIPE ASSIGNED PA ● low
217.59.136.244/30 FIMASRL RIPE ASSIGNED PA ● 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.

NIC Handles

DUMY-RIPE DUMY-RIPE INTERB-MNT TIG-MNT