Network · data from 2026-11-12
AS11006 HRT-SCS - HRTec
Registry name: HRT-SCS - HRTec, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS11006, 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.
| 2604:6940::/32 | No ROA | Other IRR onlyRADB, RIPE-NONAUTH | 633 100% |
| 2604:6940:80::/41 | No ROA | Other IRR onlyRADB | 633 100% |
AS-SET
AS11006 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: none2
- Route object: RIR2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2604:6940::/32 | No ROA covers it. Add a ROA for AS11006, maxLength 32. |
| Route object: RIR | 2604:6940::/32 | Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 2604:6940:80::/41 | No ROA covers it. Add a ROA for AS11006, maxLength 41. |
| Route object: RIR | 2604:6940:80::/41 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS11006 whose prefix no peer sees AS11006 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 216.143.113.0/24 | RADB | No ROA |
| 2604:6940:900::/41 | RIPE-NONAUTH | 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.