RU-SOVAM-Tele-Port-p2p-Net
BGP inherited
Cluster stats
| Netblocks | 2 |
| All fragments | 9 blocks across 6 clusters |
| Cluster ID | 208231555 |
| 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 | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 195.239.37.16/29 | RU-SOVAM-Tele-Port-p2p-Net | RIPE | ASSIGNED PA | ● low |
| 195.239.127.0/26 | RU-SOVAM-TELE-Port-P2P-NET | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “RU SOVAM Tele Port p2p” — 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.
- RU-SoVaM-Tele-Port-P2P-B2B-NET 2 blocks
- RU-Sovam-Tele-Port-p2p-IP-Pool-2017-12-10-NET 2 blocks
- RU-SOVAM-Tele-Port-p2p-IP-pool-NET 1 blocks
- RU-SoVaM-TELE-PORT-P2P-B2B-Client-IP-Static-PooL-NET 1 blocks
- RU-SOVAM-Tele-Port-p2p-Networks-NET 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.
- Sovam Teleport P2P Et Fttb Ip Pool sub-allocation
- Sovamteleport Pool 24 Xeth sub-allocation
- Sovam Teleport P2P Clients Pool sub-allocation
- Sovamteleport Endusers Static Pool 26 Izsvin sub-allocation
- Sovamteleport Xethr Endusers Static Pool 30 sub-allocation
- Sovamteleport Wi Fi Endusers Et P2P Pool sub-allocation
- Sovam Teleport Xether Endusers Und P2P Pool sub-allocation
- Sovam Tele Port Endusers Ip Pool And sub-allocation
NIC Handles
AS3216-MNT
DUMY-RIPE
DUMY-RIPE