SSR
Unresolved
Cluster stats
| Netblocks | 3 |
| All fragments | 21 blocks across 8 clusters |
| Cluster ID | 194106415 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 5 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 92.42.107.188/30 | SSR | RIPE | ASSIGNED PA | ● high |
| 2a01:7a7:2:1f93::/64 | SSR | RIPE | ASSIGNED | ● high |
| 2a00:2381:f832::/48 | SSR | RIPE | AGGREGATED-BY-LIR | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
Possible discrepancies (1)
These blocks are registered to SSR 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:2381:f832::/48 /48 | authorized for AS2856 — British Telecommunications PLC |
NIC Handles
BTNET-MNT
DUMY-RIPE
DUMY-RIPE
FGK-MNT
ORG-SA4361-RIPE