LEONET_ATM_PISA

BGP inherited

Cluster stats

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

IP Ranges (1)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
212.19.98.0/24	LEONET_ATM_PISA	RIPE	ASSIGNED PA	● medium

Possibly related to this organisation

what's this?

Same name family

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

Server_Leonet_Firenze via UAN COMPANY S.R.L. sub-allocation
Rete_Mobile_Leonet via UAN COMPANY S.R.L. sub-allocation
Rete_Infracom_Leonet via UAN COMPANY S.R.L. sub-allocation
LEONET_NETWORK_PUBLIC via UAN COMPANY S.R.L. sub-allocation
LEONET_ATM_FIRENZE via UAN COMPANY S.R.L. sub-allocation
LEONET_ATM_GROSSETO via UAN COMPANY S.R.L. sub-allocation
LEONET_ATM_LIVORNO via UAN COMPANY S.R.L. 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)

RPKI-inferred operator UAN COMPANY S.R.L.

Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.

No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE IT-LEONET-MNT