TETATELECOM-MOSCOW
Data as of 2026-10-04
BGP inherited
This organisation
| Netblocks | 14 · 3,072 IPv4 addresses |
| IPv6 | 2 prefixes (largest 2a04:6a40::/32) |
| Record ID | 246459402 |
| 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 | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (14)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 94.143.128.0/24 | TETATELECOM-MOSCOW | RIPE | ASSIGNED PA | ● medium |
| 94.143.129.0/24 | TETATELECOM-MOSCOW | RIPE | ASSIGNED PA | ● medium |
| 94.143.130.0/24 | TETATELECOM-MOSCOW | RIPE | ASSIGNED PA | ● medium |
| 94.143.131.0/24 | TETATELECOM-MOSCOW | RIPE | ASSIGNED PA | ● medium |
| 94.143.132.0/24 | TETATELECOM-MOSCOW | RIPE | ASSIGNED PA | ● medium |
| 94.143.133.0/24 | TETATELECOM-MOSCOW | RIPE | ASSIGNED PA | ● medium |
| 94.143.134.0/24 | TETATELECOM-MOSCOW | RIPE | ASSIGNED PA | ● medium |
| 94.143.135.0/24 | TETATELECOM-MOSCOW | RIPE | ASSIGNED PA | ● medium |
| 185.169.216.0/24 | TETATELECOM-MOSCOW | RIPE | ASSIGNED PA | ● medium |
| 185.169.217.0/24 | TETATELECOM-MOSCOW | RIPE | ASSIGNED PA | ● medium |
| 185.169.218.0/24 | TETATELECOM-MOSCOW | RIPE | ASSIGNED PA | ● medium |
| 185.169.219.0/24 | TETATELECOM-MOSCOW | RIPE | ASSIGNED PA | ● medium |
| 2a04:6a40::/36 | TETATELECOM-MOSCOW | RIPE | AGGREGATED-BY-LIR | ● medium |
| 2a04:6a40::/32 | TETATELECOM-MOSCOW | RIPE | ALLOCATED-BY-LIR | ● medium |
IPv6 ranges (2)
Footprint over time
15 weekly snapshots · JSON
14
0 netblocks since 2026-07-05
2026-07-05
peak 14
2026-10-04
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(14 of 14)
RPKI-inferred operator
"TETA TELECOM" LLC
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
TETATELECOM-MNT