TOMSK-NET
BGP inherited
Cluster stats
| Netblocks | 8 · 4,152 IPv4 addresses |
| All fragments | 19 blocks across 5 clusters |
| Cluster ID | 209644181 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 6 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
5 weekly snapshots · JSON
8
0 netblocks since 2026-07-05
2026-07-05
peak 8
2026-07-19
IP Ranges (8)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 46.29.192.0/26 | TOMSK | RIPE | ASSIGNED PA | ● low |
| 213.210.64.0/24 | TOMSK-NET | RIPE | ASSIGNED PA | ● low |
| 213.210.65.128/25 | TOMSK-NET | RIPE | ASSIGNED PA | ● low |
| 213.210.67.32 – 213.210.67.159 | TOMSK-NET | RIPE | ASSIGNED PA | ● low |
| 213.210.74.0/24 | TOMSK-NET | RIPE | ASSIGNED PA | ● low |
| 213.210.80.0/22 | TOMSK-NET | RIPE | ASSIGNED PA | ● low |
| 213.210.85.0/24 | TOMSK-NET | RIPE | ASSIGNED PA | ● low |
| 213.210.116.0 – 213.210.123.255 | TOMSK-NET | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “TOMSK” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- Tomsk City Administration 4 blocks
- Tomsk-Network 3 blocks
- Tomsk State University 3 blocks
- Tomsk-TDShkurenko 1 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- DARIMTOMSK via PJSC Rostelecom sub-allocation
- SOC-TOMSK via PJSC Rostelecom sub-allocation
- gpb-tomsk sub-allocation
- Torg Predpr Tomskij via MTS PJSC sub-allocation
- TOMSKARENA via PJSC Rostelecom sub-allocation
- Vistomsk-net sub-allocation
- TOMSKNET-HQ via PJSC Rostelecom sub-allocation
- Tomsk FSS sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(8 of 8)
Possible discrepancies (5)
These blocks are registered to TOMSK-NET 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.
| 213.210.116.0 – 213.210.123.255 /21 | authorized for AS15759 — PJSC Rostelecom |
| 213.210.80.0/22 /22 | authorized for AS15759 — PJSC Rostelecom |
| 213.210.85.0/24 /24 | authorized for AS15759 — PJSC Rostelecom |
| 213.210.74.0/24 /24 | authorized for AS15759 — PJSC Rostelecom |
| 213.210.64.0/24 /24 | authorized for AS15759 — PJSC Rostelecom |
NIC Handles
DUMY-RIPE
DUMY-RIPE
MEGAFON-AUTO-MNT
MEGAFON-RIPE-MNT
MF-SIB-MNT
ROSTELECOM-MNT