P2P-Moscow-BC-NET
BGP inherited
Cluster stats
| Netblocks | 4 |
| All fragments | 23 blocks across 5 clusters |
| Cluster ID | 208250412 |
| 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 (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 81.211.54.232/29 | P2P-Moscow-BC-NET | RIPE | ASSIGNED PA | ● low |
| 81.211.60.0/24 | P2P-Moscow-BC-NET | RIPE | ASSIGNED PA | ● low |
| 81.211.70.0/26 | P2P-Moscow-BC-NET | RIPE | ASSIGNED PA | ● low |
| 81.211.72.0/24 | P2P-Moscow-BC-NET | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “P2P Moscow” — 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.
- P2P-Moscow-NET 16 blocks
- P2P-Moscow-Wireless-NET 1 blocks
- P2P-Moscow-ARTCOM-NET 1 blocks
- P2P-Moscow_Regions-MPLS-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.
- DBEST-RU-MOSCOW via PJSC MegaFon sub-allocation
- Group Moscow via PJSC Rostelecom sub-allocation
- GIG_MOSCOW via PJSC MegaFon sub-allocation
- Moscow via PJSC MegaFon sub-allocation
- profestate-moscow-net sub-allocation
- Moscow-regional-antitubercular-clinic-Net sub-allocation
- Moscow-Financially-legal-Academy-Net sub-allocation
- Moscow-financially-legal-academy-2-Net sub-allocation
NIC Handles
AS3216-MNT
DUMY-RIPE
DUMY-RIPE