Apuacom
Registry
Cluster stats
| Netblocks | 5 |
| All fragments | 21 blocks across 2 clusters |
| Cluster ID | 213182913 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 185.1.114.61/32 | Apuacom | PEERINGDB | ASSIGNED | ● high |
| 193.42.140.31/32 | Apuacom | PEERINGDB | ASSIGNED | ● high |
| 217.29.67.196/32 | Apuacom | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:b:100:1d1:a5d5:9919:196/128 | Apuacom | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:c5::a505:9919:1/128 | Apuacom | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
80.0%
of checked blocks have valid RPKI ROA coverage
(4 of 5)
No discrepancies found among checked blocks.
NIC Handles
AS59919