Network · data from 2026-11-12
AS399852 HDD-BROADBAND - HDD Broadband Inc.
Registry name: HDD-BROADBAND - HDD Broadband Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS399852, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 2602:fc7c::/36 | No ROA | Other IRR onlyRADB | 633 100% |
| 45.59.139.0/24 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 198.62.196.0/24 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 209.112.68.0/22 | No ROA | RIR databaseARIN, RADB | 673 100% |
AS-SET
AS399852 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 8 are in fix.csv.
- ROA: none4
- Route object: RIR1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2602:fc7c::/36 | No ROA covers it. Add a ROA for AS399852, maxLength 36. |
| Route object: RIR | 2602:fc7c::/36 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 45.59.139.0/24 | No ROA covers it. Add a ROA for AS399852, maxLength 24. |
| ROA: none | 198.62.196.0/24 | No ROA covers it. Add a ROA for AS399852, maxLength 24. |
| ROA: none | 209.112.68.0/22 | No ROA covers it. Add a ROA for AS399852, maxLength 22. |
Route objects not announced
Route objects with origin AS399852 whose prefix no peer sees AS399852 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 158.51.156.0/23 | ARIN | Invalid: origin |
| 158.51.156.0/24 | ARIN | Invalid: origin |
| 158.51.157.0/24 | ARIN | Invalid: origin |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.