Network · data from 2026-11-12
AS401933 HASHIT - HashIT
Registry name: HASHIT - HashIT, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS401933, 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.
| 23.246.149.0/24 | Valid | Nonecovered by 23.246.148.0/22 | 673 100% |
| 23.182.128.0/24 | Valid | RIR databaseARIN | 673 100% |
| 23.246.148.0/24 | Valid | RIR databaseARIN | 673 100% |
| 23.246.148.0/22 | Valid | RIR databaseARIN, RADB | 671 100% |
| 64.188.7.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
AS-SET
AS401933 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 9 are in fix.csv.
- Route object: none1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 23.246.149.0/24 | No route object for it. A route object for 23.246.148.0/22 with origin AS401933 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401933 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS401933 whose prefix no peer sees AS401933 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 70.169.188.0/24 | RADB | Valid |
| 70.183.78.0/24 | RADB | Valid |
| 70.183.79.0/24 | RADB | Valid |
| 72.204.244.0/24 | RADB | Valid |
| 72.204.245.0/24 | RADB | Valid |
| 98.171.230.0/24 | RADB | Valid |
| 98.171.231.0/24 | RADB | Valid |
| 2602:f59c::/40 | ARIN | 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.