MVTELECOM
Data as of 2026-08-23
Handle
Cluster stats
| Netblocks | 4 |
| IPv6 | 2 prefixes (largest 2001:12f8:0:10::42/128) |
| Cluster ID | 229180274 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 45.68.73.130/32 | MVTELECOM | PEERINGDB | ASSIGNED | ● high |
| 200.219.147.42/32 | MVTELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:9::145:130/128 | MVTELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:10::42/128 | MVTELECOM | PEERINGDB | ASSIGNED | ● high |
IPv6 ranges (2)
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
No discrepancies found among checked blocks.
NIC Handles
AS266269