Network · data from 2026-11-12
AS401707 ARPHOST
Registry name: ARPHOST - ARPHost, LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS401707, 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.
| 64.135.0.80/28 | No ROA | Other origin only | 6 1%low visibility |
| 78.109.21.0/24 | Valid | Nonecovered by 78.109.20.0/22 | 673 100% |
| 78.109.20.0/24 | Valid | Nonecovered by 78.109.20.0/22 | 666 99% |
| 2602:f4dc:1::/48 | Valid | Nonecovered by 2602:f4dc::/40 | 636 100% |
| 2602:f899:fe::/48 | Valid | Nonecovered by 2602:f899:fe::/47 | 632 99% |
| 104.232.11.0/24 | Valid | RIR databaseARIN | 666 99% |
| 2602:f4dc::/48 | Valid | RIR databaseARIN | 632 99% |
AS-SET
PeeringDB's irr_as_set for AS401707: AS-ARPHOST. 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 (AS401707 isn't in the set, or no route object for AS401707 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 | AS401707 in it | Not covered |
|---|---|---|---|---|---|
| AS-ARPHOST | ARIN | 3 | 1 | Yes | 1 |
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: none1
- Route object: none5
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 64.135.0.80/28 | No ROA covers it. Add a ROA for AS401707, maxLength 28. |
| Route object: none | 64.135.0.80/28 | Route objects for it name AS11297, AS46172. Add a route object with origin AS401707 in the RIR database for the space. |
| Route object: none | 78.109.21.0/24 | No route object for it. A route object for 78.109.20.0/22 with origin AS401707 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401707 in the RIR database for the space. |
| Route object: none | 78.109.20.0/24 | No route object for it. A route object for 78.109.20.0/22 with origin AS401707 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401707 in the RIR database for the space. |
| Route object: none | 2602:f4dc:1::/48 | No route object for it. A route object for 2602:f4dc::/40 with origin AS401707 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401707 in the RIR database for the space. |
| Route object: none | 2602:f899:fe::/48 | No route object for it. A route object for 2602:f899:fe::/47 with origin AS401707 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401707 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS401707 whose prefix no peer sees AS401707 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 78.109.20.0/22 | ARIN | Valid |
| 2602:f4dc::/40 | ARIN | Valid |
| 2602:f899:fe::/47 | 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.