STS SERVICES AS

STS Services
Data as of 2026-07-26
GLEIF verified
LEI
636700ZJUJHYP9WW9X96
Registered name
STS SERVICES AS
Jurisdiction
NO
Ultimate parent
No parent on file in GLEIF
Cluster stats
Netblocks9
IPv6 2 prefixes (largest 2001:67c:9e8:a::7/128)
Registered in Russia (5) · KZ (2)
Cluster ID214594676
RegistryPEERINGDB
Owner jurisdictionNO
Customersfind customers using this network →
Evidence & provenance ?
Attribution GLEIF legal-entity match
Legal identityLEI 636700ZJUJHYP9WW9X96
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 · report an issue

Footprint over time

6 weekly snapshots · JSON
9 -7 netblocks since 2026-07-05
2026-07-05 peak 16 2026-07-26

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
195.12.116.7/32 STS Services PEERINGDB ASSIGNED ● high
195.12.116.8/32 STS Services PEERINGDB ASSIGNED ● high
2001:67c:9e8:a::7/128 STS Services PEERINGDB ASSIGNED ● high
2001:67c:9e8:a::8/128 STS Services PEERINGDB ASSIGNED ● high
46.231.209.48/30 STS-LAN RIPE ASSIGNED PA ● low
62.5.175.48/28 STS-N RIPE ASSIGNED PA ● low
85.114.10.32/30 STS-LAN RIPE ASSIGNED PA ● low
85.114.24.112/29 STS-LAN RIPE ASSIGNED PA ● low
178.16.152.128/30 STS-LAN RIPE ASSIGNED PA ● low

IPv6 ranges (2)

CIDR
2001:67c:9e8:a::7/128
2001:67c:9e8:a::8/128

Network trust

what's this?
RPKI hygiene: D how networks compare →
44.4% of checked blocks have valid RPKI ROA coverage (4 of 9)
No discrepancies found among checked blocks.

NIC Handles

AS207966 DUMY-RIPE DUMY-RIPE MTU-NOC OBIT-MNT