MV TELECOM
Cluster stats
| Netblocks | 21 |
| All fragments | 106 blocks across 44 clusters |
| Cluster ID | 191330515 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (21)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 170.78.96.0/22 | MV TELECOM | BGP | ANNOUNCED | ● high |
| 170.78.96.0/24 | MV TELECOM | BGP | ANNOUNCED | ● high |
| 170.78.96.0/23 | MV TELECOM | BGP | ANNOUNCED | ● high |
| 170.78.97.0/24 | MV TELECOM | BGP | ANNOUNCED | ● high |
| 170.78.98.0/24 | MV TELECOM | BGP | ANNOUNCED | ● high |
| 170.78.98.0/23 | MV TELECOM | BGP | ANNOUNCED | ● high |
| 170.78.99.0/24 | MV TELECOM | BGP | ANNOUNCED | ● high |
| 2804:351c::/32 | MV TELECOM | BGP | ANNOUNCED | ● high |
| 2804:351c::/33 | MV TELECOM | BGP | ANNOUNCED | ● high |
| 2804:351c:1111::/48 | MV TELECOM | BGP | ANNOUNCED | ● high |
| 2804:351c:1deb::/48 | MV TELECOM | BGP | ANNOUNCED | ● high |
| 2804:351c:3deb::/48 | MV TELECOM | BGP | ANNOUNCED | ● high |
| 2804:351c:8000::/33 | MV TELECOM | BGP | ANNOUNCED | ● high |
| 2804:351c:b551::/48 | MV TELECOM | BGP | ANNOUNCED | ● high |
| 170.78.96.56/30 | UNKNOWN | LACNIC | reassigned | ● medium |
| 170.78.97.48/30 | UNKNOWN | LACNIC | reassigned | ● medium |
| 170.78.97.52/30 | UNKNOWN | LACNIC | reassigned | ● medium |
| 170.78.99.128/29 | UNKNOWN | LACNIC | reassigned | ● medium |
| 2804:351c::/32 | UNKNOWN | LACNIC | allocated | ● medium |
| 2804:351c:1de8::/48 | UNKNOWN | LACNIC | reassigned | ● medium |
| 2804:351c:1de9::/48 | UNKNOWN | LACNIC | reassigned | ● medium |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(21 of 21)
No discrepancies found among checked blocks.
NIC Handles
AS266269