FAPSRL

BGP inherited
Cluster stats
Netblocks6
Cluster ID210308757
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

3 weekly snapshots · JSON
6 0 netblocks since 2026-07-12
2026-07-12 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.99.75.76/30 FAPSRL RIPE ASSIGNED PA ● low
31.199.97.4/30 FAPSRL RIPE ASSIGNED PA ● low
82.187.147.16/30 FAPSRL RIPE ASSIGNED PA ● low
88.33.241.96/29 FAPSRL RIPE ASSIGNED PA ● low
94.89.229.20/30 FAPSRL RIPE ASSIGNED PA ● low
195.103.226.200/30 FAPSRL 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