RU-BeeLine-VRN-yaNDeX-NET
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 14 blocks across 13 clusters |
| Cluster ID | 204810823 |
| 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.16.51.136/29 | RU-BeeLine-VRN-yaNDeX-NET | RIPE | ASSIGNED PA | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “RU BeeLine VRN” — 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-BeeLine-VRN-eFKo-UK-NET 2 blocks
- RU-Beeline-VRN-HoMeiNTeRieR-NET 1 blocks
- RU-Beeline-VRN-STeBooNoV-AV-NET 1 blocks
- RU-BeeLine-VRN-KeLLoGG-NET 1 blocks
- RU-Beeline-VRN-iMPeRiaL-NET 1 blocks
- RU-Beeline-VRN-GDC-Services-NET 1 blocks
- RU-BeeLine-VRN-DT-IT-RUS-NET 1 blocks
- RU-Beeline-VRN-NuMeDy-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.
- Beeline Vlv Transsvyaz sub-allocation
- Beeline Msk Styletelekom sub-allocation
- Beeline Msk Positivetechnologies sub-allocation
- Beeline Msk Cpl sub-allocation
- Beeline Msk Green sub-allocation
- Beeline Msk Vseinstrumenty Ru sub-allocation
- B2C Beeline MGMT sub-allocation
- Beeline Msk Entels sub-allocation
NIC Handles
DUMY-RIPE
DUMY-RIPE
SOVINTEL-MNT