Astound
Data as of 2026-08-09
Registry
Cluster stats
| Netblocks | 17 · 24,583 IPv4 addresses |
| IPv6 | 7 prefixes (largest 2001:504:0:2::6079:1/128) |
| All fragments | 20 blocks across 3 clusters |
| Cluster ID | 218207631 |
| 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 | 4 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
7 weekly snapshots · JSON
17
+1 netblocks since 2026-07-05
2026-07-05
peak 17
2026-08-09
IP Ranges (17)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 149.112.11.22/32 | Astound | PEERINGDB | ASSIGNED | ● high |
| 198.32.118.23/32 | Astound | PEERINGDB | ASSIGNED | ● high |
| 198.32.160.132/32 | Astound | PEERINGDB | ASSIGNED | ● high |
| 206.82.104.145/32 | Astound | PEERINGDB | ASSIGNED | ● high |
| 206.108.236.4/32 | Astound | PEERINGDB | ASSIGNED | ● high |
| 206.126.236.25/32 | Astound | PEERINGDB | ASSIGNED | ● high |
| 208.115.136.25/32 | Astound | PEERINGDB | ASSIGNED | ● high |
| 2001:504:0:2::6079:1/128 | Astound | PEERINGDB | ASSIGNED | ● high |
| 2001:504:0:4::6079:1/128 | Astound | PEERINGDB | ASSIGNED | ● high |
| 2001:504:1::a500:6079:1/128 | Astound | PEERINGDB | ASSIGNED | ● high |
| 2001:504:f::17/128 | Astound | PEERINGDB | ASSIGNED | ● high |
| 2001:504:24:1::17bf:1/128 | Astound | PEERINGDB | ASSIGNED | ● high |
| 2001:504:36::17bf:0:1/128 | Astound | PEERINGDB | ASSIGNED | ● high |
| 2001:504:102::17bf:0:1/128 | Astound | PEERINGDB | ASSIGNED | ● high |
| 9.142.160.0/19 | Astound-Communications | RIPE | LEGACY | ● low |
| 9.151.128.0/18 | Astound_NY9_NYC_2 | RIPE | LEGACY | ● low |
| 9.151.128.0/19 | Astound_Communications | RIPE | LEGACY | ● low |
IPv6 ranges (7)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
52.9%
of checked blocks have valid RPKI ROA coverage
(9 of 17)
Possible discrepancies (3)
These blocks are registered to Astound 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.
| 9.151.128.0/18 /18 | authorized for AS6079 — RCN |
| 9.142.160.0/19 /19 | authorized for AS6079 — RCN |
| 9.151.128.0/19 /19 | authorized for AS6079 — RCN |
NIC Handles
AS6079
DUMY-RIPE
DUMY-RIPE
mnt-us-aviation-1