MegaFon-Tajikistan-NET
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 4 · 768 IPv4 addresses |
| IPv6 | 1 prefix (largest 2a0b:6bc0::/36) |
| All fragments | 13 blocks across 5 clusters |
| Cluster ID | 213269900 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 109.68.232.0/24 | MegaFon-Tajikistan-NET | RIPE | ASSIGNED PA | ● low |
| 109.68.233.0/24 | MegaFon-Tajikistan-CORP-NET | RIPE | ASSIGNED PA | ● low |
| 109.68.238.0/24 | MegaFon-Tajikistan-CORP-NET | RIPE | ASSIGNED PA | ● low |
| 2a0b:6bc0::/36 | MegaFon-Tajikistan-NET | RIPE | AGGREGATED-BY-LIR | ● low |
IPv6 ranges (1)
| CIDR |
|---|
| 2a0b:6bc0::/36 |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
RPKI-inferred operator
Closed Joint Stock Company TT mobile
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
tt-mobile-MNT