SIG Telecom
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 29 · 382 IPv4 addresses |
| IPv6 | 13 prefixes (largest 2001:41e0:6000::/36) |
| Registered in | Switzerland (10) · Netherlands (3) · Germany (1) · France (1) · Poland (1) |
| Cluster ID | 213572225 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 10 shared RIR contact/maintainer handles |
| Registry names | 17 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
6 weekly snapshots · JSON
29
-11 netblocks since 2026-07-05
2026-07-05
peak 40
2026-07-26
IP Ranges (29)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 80.81.194.44/32 | SIG Telecom | PEERINGDB | ASSIGNED | ● high |
| 80.249.208.234/32 | SIG Telecom | PEERINGDB | ASSIGNED | ● high |
| 91.206.52.84/32 | SIG Telecom | PEERINGDB | ASSIGNED | ● high |
| 192.65.185.142/32 | SIG Telecom | PEERINGDB | ASSIGNED | ● high |
| 193.239.116.144/32 | SIG Telecom | PEERINGDB | ASSIGNED | ● high |
| 194.42.48.69/32 | SIG Telecom | PEERINGDB | ASSIGNED | ● high |
| 194.110.127.0/24 | SIG SP. Z O.O. | RIPE | ASSIGNED PI | ● high |
| 2001:7f8::51c4:0:1/128 | SIG Telecom | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1::a502:932:1/128 | SIG Telecom | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:c:8235:194:42:48:69/128 | SIG Telecom | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:13::a502:932:1/128 | SIG Telecom | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1c:24a::51c4:1/128 | SIG Telecom | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:24::54/128 | SIG Telecom | PEERINGDB | ASSIGNED | ● high |
| 62.177.252.112/29 | SIG-CS | RIPE | ASSIGNED PA | ● low |
| 212.157.222.8/29 | SIG-NET1 | RIPE | ASSIGNED PA | ● low |
| 217.169.131.208/28 | SIG-TELECOM-CUW-PTP | RIPE | ASSIGNED PA | ● low |
| 217.169.138.0/29 | SIG-TELECOM-SERVICES-1 | RIPE | ASSIGNED PA | ● low |
| 217.169.138.16/28 | SIG-TELECOM-D-EXT | RIPE | ASSIGNED PA | ● low |
| 217.169.138.32/28 | SIG-TELECOM-S-EXT | RIPE | ASSIGNED PA | ● low |
| 217.169.139.0/29 | SIG-TELECOM-SERVICES-3 | RIPE | ASSIGNED PA | ● low |
| 217.169.140.0/27 | SIG-TELECOM-D-1 | RIPE | ASSIGNED PA | ● low |
| 217.169.140.72/29 | SIG-TELECOM-EXT | RIPE | ASSIGNED PA | ● low |
| 2001:41e0::/48 | SIG-TELECOM-NET1 | RIPE | ASSIGNED | ● low |
| 2001:41e0:1::/48 | SIG-TELECOM-NET2 | RIPE | ASSIGNED | ● low |
| 2001:41e0:12:1::/64 | SIG-TELECOM-SERVICES-1 | RIPE | ASSIGNED | ● low |
| 2001:41e0:1000::/48 | SIG-TELECOM-NET-3 | RIPE | ASSIGNED | ● low |
| 2001:41e0:1001::/48 | SIG-TELECOM-SERVICES-2 | RIPE | AGGREGATED-BY-LIR | ● low |
| 2001:41e0:6000::/36 | SIG-TELECOM-CUST-1 | RIPE | AGGREGATED-BY-LIR | ● low |
| 2001:41e0:6000::/48 | SIG-TELECOM-PTP-LINKS | RIPE | ASSIGNED | ● low |
IPv6 ranges (13)
Network trust
what's this?
RPKI hygiene: B
how networks compare →
89.7%
of checked blocks have valid RPKI ROA coverage
(26 of 29)
Possible discrepancies (6)
These blocks are registered to SIG Telecom but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2001:41e0:6000::/36 /36 | authorized for AS20932 — Services Industriels de Geneve |
| 2001:41e0::/48 /48 | authorized for AS20932 — Services Industriels de Geneve |
| 2001:41e0:1::/48 /48 | authorized for AS20932 — Services Industriels de Geneve |
| 2001:41e0:1000::/48 /48 | authorized for AS20932 — Services Industriels de Geneve |
| 2001:41e0:6000::/48 /48 | authorized for AS20932 — Services Industriels de Geneve |
| 2001:41e0:1001::/48 /48 | authorized for AS20932 — Services Industriels de Geneve |
NIC Handles
AS20932
DUMY-RIPE
DUMY-RIPE
IWAY-NOC
NETIA-MNT
NL-BBNET-MNT
ORG-WPSZ1-RIPE
RIPE-NCC-END-MNT
SIG-TELECOM-MNT
TKPSA-MNT