OLISYS-OLISYS-LAON

BGP inherited

Cluster stats

Netblocks	1
All fragments	4 blocks across 4 clusters
Cluster ID	204798038
Registry	RIPE
Customers	find 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

IP Ranges (1)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
109.7.11.64/30	OLISYS-OLISYS-LAON	RIPE	ASSIGNED PA	● medium

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “OLISYS OLISYS” — 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.

OLISYS-OLISYS-SOISSONS 1 blocks
OLISYS-OLISYS-PARIS-08 1 blocks
OLISYS-OLISYS-VILLENEUVE-ST-GERMAIN 1 blocks

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.

OLISYS-OLISYS-SOISSONS via Societe Francaise Du Radiotelephone - SFR SA sub-allocation
OLISYS-OLISYS-PARIS-08 via Societe Francaise Du Radiotelephone - SFR SA sub-allocation
OLISYS-OLISYS-VILLENEUVE-ST-GERMAIN via Societe Francaise Du Radiotelephone - SFR SA sub-allocation
OLISYS-LAON via Societe Francaise Du Radiotelephone - SFR SA sub-allocation
OLISYS-LK-SOISSONS via Societe Francaise Du Radiotelephone - SFR SA sub-allocation
OLISYS-BEZANNES via Societe Francaise Du Radiotelephone - SFR SA sub-allocation
OLISYS-LAON-LAON via Societe Francaise Du Radiotelephone - SFR SA sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

100.0% of checked blocks have valid RPKI ROA coverage (1 of 1)

No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE LDCOM-MNT LDCOM-PRO-MNT