STS-NET-1

Data as of 2026-07-26
BGP inherited
Limited data: only 3 ranges found registered under this exact name. This may not reflect the organisation's full internet footprint — many companies' web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
Netblocks3
IPv6 2 prefixes (largest 2001:4dd0:d7fa::/48)
Cluster ID214697772
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (3)

⬇ export CSV
CIDR Org name Registry Status Confidence
195.98.200.176/28 STS-NET-1 RIPE ASSIGNED PA ● low
2001:4dd0:d7fa::/48 STS-1 RIPE ASSIGNED ● low
2a00:5da1:100::/48 STS-NET-1 RIPE ASSIGNED ● low

IPv6 ranges (2)

Network trust

what's this?
RPKI hygiene: C how networks compare →
66.7% of checked blocks have valid RPKI ROA coverage (2 of 3)
Possible discrepancies (1)

These blocks are registered to STS-NET-1 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.

2a00:5da1:100::/48 /48 authorized for AS207966 — AO "State Technical Service"

NIC Handles

DUMY-RIPE DUMY-RIPE Maxat_Nessipbekov-MNT NETCOLOGNE-MNT PLANET-MNT