MGNT-VLN-LT
BGP inherited
Cluster stats
| Netblocks | 7 · 12,793 IPv4 addresses |
| All fragments | 8 blocks across 2 clusters |
| Cluster ID | 209238833 |
| 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 | |
Footprint over time
5 weekly snapshots · JSON
7
0 netblocks since 2026-07-05
2026-07-05
peak 7
2026-07-19
IP Ranges (7)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 88.223.4.0 – 88.223.15.255 | MGNT-VLN-LT | RIPE | ASSIGNED PA | ● low |
| 88.223.24.0/21 | MGNT-VLN-LT | RIPE | ASSIGNED PA | ● low |
| 88.223.32.0/21 | MGNT-VLN-LT | RIPE | ASSIGNED PA | ● low |
| 88.223.40.0/23 | MGNT-VLN-LT | RIPE | ASSIGNED PA | ● low |
| 88.223.48.0/21 | MGNT-VLN-LT | RIPE | ASSIGNED PA | ● low |
| 88.223.56.0/21 | MGNT-VLN-LT | RIPE | ASSIGNED PA | ● low |
| 88.223.64.0/22 | MGNT-VLN-LT | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “MGNT VLN LT” — 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.
- MGNT-VLN-LT-BACKBONE 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.
- HSO-MORLEY-GROUP-MGNT via Syntura Group Limited sub-allocation
- Facilities-Mgnt-Recruitment via Vodafone Limited sub-allocation
- Mgnt Vr via PFALZKOM GmbH sub-allocation
- MGNT-VLN-LT-BACKBONE via UAB INIT sub-allocation
- GRIFFIN-LON-TCHX-MGNT sub-allocation
- OLMAN-WTEO-MGNT sub-allocation
- THALES-TSL-QUAD-IDMGNT via BNW TECHNOLOGY LTD sub-allocation
- Duocast Mgnt via Duocast B.V. sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(7 of 7)
RPKI-inferred operator
UAB INIT
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
INIT-LT