Network · data from 2026-11-12
AS40784 HIQDATA - hiQ Data Corporation
Registry name: HIQDATA - hiQ Data Corporation, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS40784, 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.
| 162.223.208.0/21 | Invalid: origin | Other origin only | 2 0%low visibility |
| 192.199.208.0/20 | No ROA | Other IRR onlyALTDB | 670 100% |
AS-SET
AS40784 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 6 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none1
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 162.223.208.0/21 | ROAs covering it name AS11885, not AS40784. If AS40784 should announce it, add a ROA for AS40784. |
| Route object: none | 162.223.208.0/21 | Route objects for it name AS11885. Add a route object with origin AS40784 in the RIR database for the space. |
| ROA: none | 192.199.208.0/20 | No ROA covers it. Add a ROA for AS40784, maxLength 20. |
| Route object: RIR | 192.199.208.0/20 | Route object only in ALTDB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS40784 whose prefix no peer sees AS40784 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.83.80.0/21 | ALTDB | No ROA |
| 38.126.200.0/22 | ALTDB | No ROA |
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.