TOMSKNET-TTS
Cluster stats
| Netblocks | 3 |
| All fragments | 56 blocks across 3 clusters |
| Cluster ID | 191950843 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 4 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 |
|---|---|---|---|---|
| 217.18.136.48/29 | TOMSKNET-TTS | RIPE | ASSIGNED PA | ● low |
| 217.18.143.128/26 | TOMSKNET-TTS | RIPE | ASSIGNED PA | ● low |
| 217.18.144.0/24 | TOMSKNET-TTS | RIPE | ASSIGNED PA | ● 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 TOMSKNET-TTS 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.
| 217.18.144.0/24 /24 | authorized for AS15759 — PJSC Rostelecom |
NIC Handles
DIN-RIPE-MNT
DUMY-RIPE
DUMY-RIPE
ROSTELECOM-MNT