Network · data from 2026-11-12
AS214618 Hack The Box
Registry name: HTB-AS Hack The Box Single Member Private Company, GR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS214618, 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.
| 154.57.19.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 154.57.164.0/22 | No ROA | Other IRR onlyRADB | 670 100% |
| 146.103.60.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 45.149.101.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 109.176.239.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 38.27.140.0/22 | Valid | RIR databaseARIN | 671 100% |
| 92.112.68.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 31.56.181.0/24 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 2a14:7240:e02::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a14:7240:e03::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a14:7240:a10::/48 | Valid | RIR databaseRADB, RIPE | 634 100% |
| 2a14:7240:e01c::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS214618: AS214618:AS-HTB. 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 (AS214618 isn't in the set, or no route object for AS214618 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 | AS214618 in it | Not covered |
|---|---|---|---|---|---|
| AS214618:AS-HTB | RIPE | 4 | 3 | Yes | 0 |
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.
- ROA: none2
- Route object: RIR2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 154.57.19.0/24 | No ROA covers it. Add a ROA for AS214618, maxLength 24. |
| Route object: RIR | 154.57.19.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 154.57.164.0/22 | No ROA covers it. Add a ROA for AS214618, maxLength 22. |
| Route object: RIR | 154.57.164.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS214618 whose prefix no peer sees AS214618 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:470:3b4::/48 | ARIN | Valid |
| 2001:470:4a3::/48 | ARIN | Valid |
| 2001:470:5fb::/48 | ARIN | Valid |
| 2a14:7240:a01c::/48 | RIPE | No ROA |
| 2a14:7240:dead::/48 | RIPE | 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.