Tander
TANDER
Registry
Cluster stats
| Netblocks | 5 |
| All fragments | 47 blocks across 22 clusters |
| Cluster ID | 191877502 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 5 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 62.5.134.144/28 | TANDER | RIPE | ASSIGNED PA | ● low |
| 94.25.8.100/30 | Tander | RIPE | ASSIGNED PA | ● low |
| 95.167.14.52/30 | TANDER | RIPE | ASSIGNED PA | ● low |
| 95.167.43.0/24 | Tander | RIPE | ASSIGNED PA | ● low |
| 149.62.54.4/30 | tander | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
80.0%
of checked blocks have valid RPKI ROA coverage
(4 of 5)
Possible discrepancies (1)
These blocks are registered to TANDER 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.
| 95.167.43.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
NIC Handles
DUMY-RIPE
DUMY-RIPE
LINENEW-MNT
MTU-NOC
ROSTELECOM-MNT