RU-BeeLine-FTTB-B2B-clients-NET
BGP inherited
Cluster stats
| Netblocks | 2 |
| All fragments | 4 blocks across 3 clusters |
| Cluster ID | 205551048 |
| 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 |
|---|---|---|---|---|
| 81.9.125.0/24 | RU-BeeLine-FTTB-B2B-Clients-NET | RIPE | ASSIGNED PA | ● low |
| 81.222.197.0/24 | RU-BeeLine-FTTB-B2B-clients-NET | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “RU BeeLine FTTB” — 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-FTTB-client-pool-NET 1 blocks
- RU-BeeLine-FTTB-clients-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 Omsk B2B Fttb Clients sub-allocation
- Beeline Saratov Fttb sub-allocation
- Beeline Fttb Client Pool sub-allocation
- Beeline Fttb Clients sub-allocation
NIC Handles
AS3216-MNT
DUMY-RIPE
DUMY-RIPE