SIPARTECH
Sipartech
Data as of 2026-07-26
GLEIF verified
Complete entity footprint
2 linked clusters ·
54 netblocks ·
71,192 IPv4 addresses ·
23 IPv6 prefixes
This organisation's clusters combined by evidence —
shared GLEIF corporate family
— not name similarity, so genuinely different organisations that share a name are excluded.
LEI
969500L70OZNWG46F581
Registered name
SIPARTECH
Jurisdiction
Ultimate parent
No parent on file in GLEIF
Cluster stats
| Netblocks | 33 |
| IPv6 | 15 prefixes (largest 2001:504:0:2::8309:1/128) |
| Registered in | United States (6) · Netherlands (4) · Germany (3) · France (3) · United Kingdom (2) |
| All fragments | 58 blocks across 2 clusters |
| Cluster ID | 214582860 |
| Registry | PEERINGDB |
| Owner jurisdiction | FR |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | GLEIF legal-entity match |
| Legal identity | LEI 969500L70OZNWG46F581 |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
6 weekly snapshots · JSON
33
0 netblocks since 2026-07-05
2026-07-05
peak 33
2026-07-26
IP Ranges (33)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 37.49.232.95/32 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 37.49.237.47/32 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 62.69.146.121/32 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 80.81.195.6/32 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 80.249.211.152/32 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 185.1.47.12/32 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 193.239.119.214/32 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 195.42.144.170/32 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 195.66.226.125/32 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 195.66.238.125/32 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 198.32.243.112/32 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 206.72.210.101/32 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 206.81.81.86/32 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 206.82.104.47/32 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 206.126.115.161/32 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 206.126.237.197/32 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 2001:504:0:2::8309:1/128 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 2001:504:0:6:0:1:8309:1/128 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 2001:504:13::210:101/128 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 2001:504:16::2075/128 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 2001:504:36::2075:0:1/128 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8::2075:0:1/128 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1::a500:8309:1/128 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:4::2075:1/128 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:4:1::2075:1/128 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:8:20:0:2075:0:1/128 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:13::a500:8309:1/128 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:36::2075:0:1/128 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:43::8309:1/128 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:54::1:47/128 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:54:5::95/128 | Sipartech | PEERINGDB | ASSIGNED | ● high |
| 85.233.195.208/30 | SIPARTECH | RIPE | ASSIGNED PA | ● low |
| 85.233.195.212/30 | SIPARTECH | RIPE | ASSIGNED PA | ● low |
IPv6 ranges (15)
Corporate group (2 confirmed entities)
+3 additional unconfirmed candidates not shown — full list (JSON)- SIPARTECH SAS 25 blocks
Network trust
what's this?
RPKI hygiene: B
how networks compare →
84.8%
of checked blocks have valid RPKI ROA coverage
(28 of 33)
No discrepancies found among checked blocks.
NIC Handles
AS8309
DUMY-RIPE
DUMY-RIPE
EQUINIX-MNT