MECOM-NET
BGP inherited
Cluster stats
| Netblocks | 4 |
| All fragments | 13 blocks across 8 clusters |
| Cluster ID | 205532318 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| 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 (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 193.109.231.0/24 | MECOM-NET | RIPE | ASSIGNED PI | ● high |
| 91.25.181.120/29 | MECOM-NET | RIPE | ASSIGNED PA | ● low |
| 195.122.193.112/28 | MECOM | RIPE | ASSIGNED PA | ● low |
| 2003:ef:f027::/48 | MECOM-NET | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
Possible discrepancies (1)
These blocks are registered to MECOM-NET 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.
| 193.109.231.0/24 /24 | authorized for AS20546 — SOPRADO GmbH |
NIC Handles
DE-COLT-MNT
DIALTELECOM-MNT
DTAG-NIC
DUMY-RIPE
DUMY-RIPE
MECOM-MNT
ORG-MCGm1-RIPE
RIPE-NCC-END-MNT