BE-PROXIMUS-MVNE
BGP inherited
Cluster stats
| Netblocks | 4 |
| All fragments | 6 blocks across 3 clusters |
| Cluster ID | 204795144 |
| 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.169.112.0/22 | BE-PROXIMUS-MVNE | RIPE | ASSIGNED PA | ● low |
| 178.145.132.0/22 | BE-PROXIMUS-MVNE | RIPE | ASSIGNED PA | ● low |
| 178.145.136.0/22 | BE-PROXIMUS-MVNE | RIPE | ASSIGNED PA | ● low |
| 178.145.156.0 – 178.145.158.255 | BE-PROXIMUS-MVNE | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “BE PROXIMUS MVNE” — 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.
- BE-PROXIMUS-MVNE-CARLI 1 blocks
- BE-PROXIMUS-MVNE-MECH 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.
- Proximus Mvne Carli via Proximus NV sub-allocation
- Proximus Mvne Mech via Proximus NV sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
SKYNETBE-MNT