SDIS64

BGP inherited

Cluster stats

Netblocks	6
All fragments	10 blocks across 5 clusters
Cluster ID	209376365
Registry	PEERINGDB
Customers	find customers using this network →

Evidence & provenance ?

Attribution	BGP parent (inherited)
Shared handles	clustered on 5 shared RIR contact/maintainer handles
Registry names	3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON

6 0 netblocks since 2026-07-05

2026-07-05 peak 6 2026-07-13

IP Ranges (6)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
185.1.169.18/32	SDIS64	PEERINGDB	ASSIGNED	● high
2001:7f8:f4::21:2324:1/128	SDIS64	PEERINGDB	ASSIGNED	● high
78.155.131.152/29	SDIS64	RIPE	ASSIGNED PA	● low
78.155.144.40/29	SDIS64	RIPE	ASSIGNED PA	● low
91.151.112.144/29	SDIS64	RIPE	ASSIGNED PA	● low
185.182.171.240/28	NET_SDIS64	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

what's this?

Same name family

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

SDIS64-LAN-OUEST 1 blocks
SDIS64-LAN-SUD 1 blocks
SDIS64-LAN 1 blocks
SDIS64-LAN-EST 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.

SDIS64-LAN-OUEST via Izarlink SAS sub-allocation
SDIS64-LAN-SUD via Izarlink SAS sub-allocation
SDIS64-LAN via Izarlink SAS sub-allocation
SDIS64-LAN-EST via Izarlink SAS sub-allocation

Network trust

what's this?

RPKI hygiene: C how networks compare →

66.7% of checked blocks have valid RPKI ROA coverage (4 of 6)

No discrepancies found among checked blocks.

NIC Handles

ALTITUDETELECOM-MNT AS212324 DUMY-RIPE DUMY-RIPE fr-izarlink-1-mnt