MTT-VOIP-NVS-INFRASTRUCTURE
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 4 blocks across 4 clusters |
| Cluster ID | 208561313 |
| 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 | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 80.75.137.0/24 | MTT-VOIP-NVS-INFRASTRUCTURE | RIPE | ASSIGNED PA | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “MTT VOIP” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- MTT-VOIP-MSK-INFRASTRUCTURE 1 blocks
- MTT-VOIP-RND-INFRASTRUCTURE 1 blocks
- MTT-VOIP-SMR-INFRASTRUCTURE 1 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- TEST-INET-VOIP-LAN via PJSC MegaFon sub-allocation
- Voip via PFALZKOM GmbH sub-allocation
- Vo IP ACME pristup Internetu via Crnogorski Telekom a.d.Podgorica sub-allocation
- KBNORD-VOIP-SE sub-allocation
- Voip via TeleData GmbH sub-allocation
- DIDWW-NET-VOIP sub-allocation
- TOOKAZVOIP via JSC Kazakhtelecom sub-allocation
- NETTE-VOIP-ZEMBORZYCE sub-allocation
NIC Handles
DUMY-RIPE
DUMY-RIPE
MTT-RIPE-MNT