RU-SOVAM-Tele-Port-B2B-client-IP-pool-NET
BGP inherited
Cluster stats
| Netblocks | 3 |
| All fragments | 4 blocks across 2 clusters |
| Cluster ID | 205361685 |
| 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 (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 81.211.79.0/24 | RU-SOVAM-Tele-Port-B2B-client-IP-pool-NET | RIPE | ASSIGNED PA | ● low |
| 194.186.34.0/24 | RU-SOVAM-Tele-PORT-B2B-client-IP-pool-NET | RIPE | ASSIGNED PA | ● low |
| 194.186.178.64 – 194.186.178.207 | RU-SOVAM-Tele-Port-B2B-client-IP-pool-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 B2B client IP” — 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.
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 Clients Pool sub-allocation
- Sovam Tele Port Clients Ip Pool sub-allocation
- Sovam Tele Port Client Ip Pool sub-allocation
- Sovam Teleport Pool B2B Clients sub-allocation
- Sovam Tele Port B2B Client sub-allocation
- Sovam Tele Port Xethernet Client Ip Pool sub-allocation
- Sovam Teleport B2B Fttb Client Ip Pool sub-allocation
- Sovam Tele Port B2B P2P Client Ip Static Pool sub-allocation
NIC Handles
DUMY-RIPE
DUMY-RIPE
SOVINTEL-MNT