INETCOM
Unresolved
Cluster stats
| Netblocks | 25 |
| All fragments | 66 blocks across 10 clusters |
| Cluster ID | 192524769 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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
2 weekly snapshots · JSON
25
0 netblocks since 2026-07-05
2026-07-05
peak 25
2026-07-06
IP Ranges (25)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 37.49.238.75/32 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 80.249.210.207/32 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 91.221.180.192/32 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 91.240.225.188/32 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 109.239.137.173/32 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 178.18.226.101/32 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 185.232.60.153/32 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 193.106.113.46/32 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 193.110.13.175/32 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 194.68.123.34/32 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 194.68.128.51/32 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 195.66.224.242/32 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 195.208.209.66/32 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1::a503:5598:1/128 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:4::8b0e:1/128 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d:fe::51/128 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d:ff::34/128 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:20:101::209:66/128 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:21:9::175/128 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:54::2:75/128 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 2001:b28:3ff::8b0e:0:1/128 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 2a00:1b30::a46/128 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4::226:101/128 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 2a0d:e180::60:153/128 | INETCOM | PEERINGDB | ASSIGNED | ● high |
| 94.100.2.0/24 | INETCOM-NET | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
68.0%
of checked blocks have valid RPKI ROA coverage
(17 of 25)
Possible discrepancies (1)
These blocks are registered to INETCOM 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.
| 94.100.2.0/24 /24 | authorized for AS47570 — SIA Tet |
NIC Handles
AS35598
DUMY-RIPE
DUMY-RIPE
INETCOMLV-MNT