INET Communication
Data as of 2026-08-16
BGP inherited
Cluster stats
| Netblocks | 4 · 769 IPv4 addresses |
| Cluster ID | 222475615 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 11 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
3 weekly snapshots · JSON
27
0 netblocks since 2026-07-05
2026-07-05
peak 27
2026-07-12
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 45.68.34.199/32 | INET Communication | PEERINGDB | ASSIGNED | ● high |
| 45.175.64.0/24 | INET Communication | LACNIC | REALLOCATED | ● low |
| 45.238.140.0/24 | INET Communication | ARIN | REALLOCATED | ● low |
| 131.161.52.0/24 | INET Communication | ARIN | REALLOCATED | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
75.0%
of checked blocks have valid RPKI ROA coverage
(3 of 4)
Possible discrepancies (2)
These blocks are registered to INET Communication 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.
| 45.175.64.0/24 /24 | authorized for AS263686 — AS263686 |
| 131.161.52.0/24 /24 | authorized for AS263686 — AS263686 |
NIC Handles
AS263686
DAC43
DAC43
DAC43
DAC43
DAC43
DAC43
HN-INCO2-LACNIC
HN-INCO5-LACNIC
HN-INET-LACNIC
HN-INET-LACNIC