RO-STS1
Data as of 2026-10-11
BGP inherited
This organisation
| Netblocks | 2 |
| IPv6 | 2 prefixes (largest 2a00:5dc1::/32) |
| Also registered under this name | 3 netblocks across 2 separate records |
| Record ID | 248339771 |
| Registry | RIPE |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 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 (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a00:5dc1::/32 | RO-STS1 | RIPE | ASSIGNED | ● low |
| 2a00:5dc2:1::/48 | RO-STS1-net | RIPE | ASSIGNED | ● low |
IPv6 ranges (2)
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
RPKI-inferred operator
Serviciul de Telecomunicatii Speciale
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
ROSTS-MNT