Maxicom
Registry
Cluster stats
| Netblocks | 6 |
| All fragments | 8 blocks across 2 clusters |
| Cluster ID | 208802454 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
4 weekly snapshots · JSON
6
0 netblocks since 2026-07-05
2026-07-05
peak 6
2026-07-19
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 185.0.20.156/32 | Maxicom | PEERINGDB | ASSIGNED | ● high |
| 185.0.20.157/32 | Maxicom | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:7f::156/128 | Maxicom | PEERINGDB | ASSIGNED | ● high |
| 185.71.40.0/27 | Maxicom | RIPE | ASSIGNED PA | ● low |
| 185.71.40.32/27 | Maxicom | RIPE | ASSIGNED PA | ● low |
| 185.71.40.64 – 185.71.40.255 | Maxicom | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(3 of 6)
No discrepancies found among checked blocks.
NIC Handles
AS201548
DUMY-RIPE
DUMY-RIPE
MNT-MZELENKA