METROCOM
Cluster stats
| Netblocks | 31 |
| All fragments | 42 blocks across 11 clusters |
| Cluster ID | 191873413 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 8 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (31)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 80.247.176.0/24 | METROCOM | RIPE | ASSIGNED PA | ● low |
| 80.247.177.0/24 | METROCOM | RIPE | ASSIGNED PA | ● low |
| 80.247.184.112/28 | METROCOM | RIPE | ASSIGNED PA | ● low |
| 80.247.184.128/26 | METROCOM | RIPE | ASSIGNED PA | ● low |
| 80.247.184.208/28 | METROCOM | RIPE | ASSIGNED PA | ● low |
| 80.247.184.224/27 | METROCOM | RIPE | ASSIGNED PA | ● low |
| 80.247.185.192/26 | METROCOM | RIPE | ASSIGNED PA | ● low |
| 114.23.148.64/27 | METROCOM-NET | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 114.23.204.128/27 | METROCOM-NET | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 114.23.234.64/27 | METROCOM-NET | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 114.23.237.32/27 | METROCOM-NET | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 114.23.241.41 – 114.23.241.70 | METROCOM-NET | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 114.23.245.32/28 | METROCOM-NET | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 114.23.245.64/27 | METROCOM-NET | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 195.5.128.0/22 | METROCOM | RIPE | ASSIGNED PA | ● low |
| 195.5.133.0/24 | METROCOM | RIPE | ASSIGNED PA | ● low |
| 195.5.135.0/24 | METROCOM | RIPE | ASSIGNED PA | ● low |
| 195.5.138.0/24 | METROCOM | RIPE | ASSIGNED PA | ● low |
| 195.5.139.0/24 | METROCOM | RIPE | ASSIGNED PA | ● low |
| 195.5.144.0/24 | METROCOM | RIPE | ASSIGNED PA | ● low |
| 195.5.149.0/24 | METROCOM | RIPE | ASSIGNED PA | ● low |
| 195.5.154.240/28 | METROCOM | RIPE | ASSIGNED PA | ● low |
| 212.119.160.0/24 | METROCOM | RIPE | ASSIGNED PA | ● low |
| 212.119.164.80/28 | METROCOM | RIPE | ASSIGNED PA | ● low |
| 212.119.164.96/27 | METROCOM | RIPE | ASSIGNED PA | ● low |
| 212.119.178.0/24 | METROCOM | RIPE | ASSIGNED PA | ● low |
| 212.119.184.0/24 | METROCOM | RIPE | ASSIGNED PA | ● low |
| 213.182.161.160/27 | METROCOM | RIPE | ASSIGNED PA | ● low |
| 213.182.163.0/24 | METROCOM | RIPE | ASSIGNED PA | ● low |
| 213.182.187.128/25 | METROCOM | RIPE | ASSIGNED PA | ● low |
| 213.182.190.0/24 | METROCOM | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
77.4%
of checked blocks have valid RPKI ROA coverage
(24 of 31)
Possible discrepancies (14)
These blocks are registered to METROCOM 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.
| 195.5.128.0/22 /22 | authorized for AS20632 — PJSC MegaFon |
| 195.5.149.0/24 /24 | authorized for AS20632 — PJSC MegaFon |
| 195.5.135.0/24 /24 | authorized for AS20632 — PJSC MegaFon |
| 195.5.138.0/24 /24 | authorized for AS20632 — PJSC MegaFon |
| 195.5.139.0/24 /24 | authorized for AS20632 — PJSC MegaFon |
| 212.119.178.0/24 /24 | authorized for AS20632 — PJSC MegaFon |
| 212.119.160.0/24 /24 | authorized for AS20632 — PJSC MegaFon |
| 212.119.184.0/24 /24 | authorized for AS20632 — PJSC MegaFon |
| 213.182.163.0/24 /24 | authorized for AS20632 — PJSC MegaFon |
| 213.182.190.0/24 /24 | authorized for AS20632 — PJSC MegaFon |
| 195.5.144.0/24 /24 | authorized for AS20632 — PJSC MegaFon |
| 195.5.133.0/24 /24 | authorized for AS20632 — PJSC MegaFon |
| 80.247.176.0/24 /24 | authorized for AS20632 — PJSC MegaFon |
| 80.247.177.0/24 /24 | authorized for AS20632 — PJSC MegaFon |
NIC Handles
AS6850-MNT
AV316-AP
AW826-AP
AW826-AP
DUMY-RIPE
DUMY-RIPE
MAINT-VOYAGERNET-NZ
MNT-MF-NWGSM