FR-ORKYN--LB_INTERNET

BGP inherited
Cluster stats
Netblocks7
All fragments 15 blocks across 4 clusters
Cluster ID210174999
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
92.175.80.231/32 FR-ORKYN--LB_INTERNET RIPE ASSIGNED PA ● low
92.175.80.241/32 FR-ORKYN--LB_INTERNET RIPE ASSIGNED PA ● low
194.51.38.178/32 FR-ORKYN--LB_INTERNET RIPE ASSIGNED PA ● low
194.51.224.200/32 FR-ORKYN--LB_INTERNET RIPE ASSIGNED PA ● low
194.250.20.70/32 FR-ORKYN--LB_INTERNET RIPE ASSIGNED PA ● low
195.101.4.242/32 FR-ORKYN--LB_INTERNET RIPE ASSIGNED PA ● low
195.101.203.50/32 FR-ORKYN---LB_INTERNET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “FR ORKYN” — 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 (7 of 7)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE PC80199-MNT