Network · data from 2026-11-12
AS998 HypeStatus
Registry name: HYPESTATUS - HypeStatus Inc, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS998, 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.
| 63.92.64.0/21 | No ROA | None | 673 100% |
| 2607:e400:3::/48 | No ROA | None | 398 63% |
| 184.174.18.0/23 | No ROA | RIR databaseARIN | 673 100% |
| 165.49.209.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 104.254.188.0/22 | Valid | RIR databaseARIN | 673 100% |
| 193.25.166.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 205.186.122.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 208.94.140.0/22 | Valid | RIR databaseARIN | 673 100% |
| 45.38.26.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 2602:f870::/36 | Valid | RIR databaseARIN | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS998: RS-HYPE. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS998 isn't in the set, or no route object for AS998 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS998 in it | Not covered | |
|---|---|---|---|---|---|---|
| RS-HYPE | A route-set, not an AS-SET; route-sets aren't expanded. | |||||
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: none3
- Route object: none2
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 63.92.64.0/21 | No ROA covers it. Add a ROA for AS998, maxLength 21. |
| Route object: none | 63.92.64.0/21 | No route object for it. Add a route object with origin AS998 in the RIR database for the space. |
| ROA: none | 2607:e400:3::/48 | No ROA covers it. Add a ROA for AS998, maxLength 48. |
| Route object: none | 2607:e400:3::/48 | No route object for it. Add a route object with origin AS998 in the RIR database for the space. |
| ROA: none | 184.174.18.0/23 | No ROA covers it. Add a ROA for AS998, maxLength 23. |
| Route object: RIR | 165.49.209.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS998 whose prefix no peer sees AS998 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:470:335::/48 | ARIN | Invalid: origin |
| 2a14:d281::/32 | 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.