Network · data from 2026-11-12
AS402857 HTOCSL - Highland
Registry name: HTOCSL - Highland, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS402857, 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.
| 151.242.67.0/24 | Invalid: origin | None | 1 0%low visibility |
| 151.245.60.0/24 | Invalid: origin | None | 1 0%low visibility |
AS-SET
AS402857 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 10 are in fix.csv.
- ROA: origin2
- Route object: none2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 151.242.67.0/24 | ROAs covering it name AS834, not AS402857. If AS402857 should announce it, add a ROA for AS402857. |
| Route object: none | 151.242.67.0/24 | No route object for it. Add a route object with origin AS402857 in the RIR database for the space. |
| ROA: origin | 151.245.60.0/24 | ROAs covering it name AS834, AS205886, not AS402857. If AS402857 should announce it, add a ROA for AS402857. |
| Route object: none | 151.245.60.0/24 | No route object for it. Add a route object with origin AS402857 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS402857 whose prefix no peer sees AS402857 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 134.202.17.0/24 | ARIN | Valid |
| 154.84.166.0/24 | AFRINIC | Invalid: origin |
| 154.86.2.0/24 | AFRINIC | Invalid: origin |
| 154.86.3.0/24 | AFRINIC | Invalid: origin |
| 154.86.6.0/24 | AFRINIC | Invalid: origin |
| 201.24.230.0/24 | RADB, RIPE | Valid |
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.