RU-SoVaM-TelePort-P2P-B2B-Client-IP-Static-PooL-NET
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 7 blocks across 7 clusters |
| Cluster ID | 207769227 |
| 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 |
|---|---|---|---|---|
| 195.239.149.0/24 | RU-SoVaM-TelePort-P2P-B2B-Client-IP-Static-PooL-NET | RIPE | ASSIGNED PA | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “RU SoVaM TelePort 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-TELEPORT-p2p-et-FTTB-IP-pool-NET 1 blocks
- RU-SOVAM-TELEPORT-p2p-Clients-pool-NET 1 blocks
- RU-SOVAM-TelePort-p2p-Clients-IP-Pool-NET 1 blocks
- RU-SOVAM-TelePort-p2p-et-users-IP-pool-NET 1 blocks
- RU-SOVAM-TelePort-p2p-et-LoopBacks-NET 1 blocks
- RU-Sovam-Teleport-P2P-EndUser-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
- Sovamteleport Msk Beeline Wi Fi sub-allocation
NIC Handles
DUMY-RIPE
DUMY-RIPE
SOVINTEL-MNT