Metro MPLS
Data as of 2026-08-09
BGP inherited
Limited data: only 2 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 2 · 520 IPv4 addresses |
| Cluster ID | 218580053 |
| Registry | LACNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 12 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
3 weekly snapshots · JSON
186
0 netblocks since 2026-07-05
2026-07-05
peak 186
2026-07-12
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 179.63.192.0/29 | Metro MPLS | LACNIC | REALLOCATED | ● low |
| 190.14.16.0/23 | Metro MPLS | LACNIC | REALLOCATED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
Possible discrepancies (1)
These blocks are registered to Metro MPLS but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 190.14.16.0/23 /23 | authorized for AS262248 — AS262248 |
NIC Handles
GUP6
GUP6
GUP6
GUP6
GUP6
GUP6
JOI2
JOI2
PA-MEMP-LACNIC
PA-MEMP-LACNIC
PA-MEMP1-LACNIC
PA-MEMP1-LACNIC