RECEPTUM

BGP inherited
Cluster stats
Netblocks8 · 300 IPv4 addresses
Registered in Finland (6) · Sweden (2)
All fragments 12 blocks across 5 clusters
Cluster ID208866430
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.15.32.184/29 RECEPTUM-OY-NET RIPE ASSIGNED PA ● low
31.15.40.96/27 RECEPTUM-OY-NET RIPE ASSIGNED PA ● low
62.71.25.128/26 RECEPTUM-NET RIPE ASSIGNED PA ● low
62.236.63.0/25 RECEPTUM RIPE ASSIGNED PA ● low
62.237.43.80/29 RECEPTUM RIPE ASSIGNED PA ● low
62.237.196.0/27 RECEPTUM RIPE ASSIGNED PA ● low
62.237.206.192/27 RECEPTUM RIPE ASSIGNED PA ● low
62.237.206.228/30 RECEPTUM RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “RECEPTUM” — 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: 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

DATANET-NOC DUMY-RIPE DUMY-RIPE FI2G-MNT SWIPNET-LIR-MNT TDC-SE-MNT