Network · data from 2026-11-12
AS14397 1st Class Hosting
Registry name: AS-DNS - 1st Class Hosting, LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS14397, 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.
| 104.251.115.0/24 | No ROA | Nonecovered by 104.251.114.0/23 | 2 0%low visibility |
| 104.251.116.0/24 | No ROA | Other origin only | 2 0%low visibility |
| 104.251.121.0/24 | No ROA | None | 2 0%low visibility |
| 192.55.95.0/24 | No ROA | Other IRR onlyALTDB | 671 100% |
| 104.251.117.0/24 | No ROA | RIR databaseARIN | 2 0%low visibility |
| 104.251.124.0/24 | Valid | Nonecovered by 104.251.124.0/22 | 671 100% |
| 104.251.125.0/24 | Valid | Nonecovered by 104.251.124.0/22 | 671 100% |
| 104.251.126.0/24 | Valid | Nonecovered by 104.251.124.0/22 | 671 100% |
| 65.49.128.0/24 | Valid | RIR databaseARIN | 671 100% |
| 65.49.129.0/24 | Valid | RIR databaseARIN | 671 100% |
| 104.251.118.0/24 | Valid | RIR databaseARIN | 671 100% |
| 104.251.127.0/24 | Valid | RIR databaseARIN | 671 100% |
AS-SET
AS14397's PeeringDB record names no 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 17 are in fix.csv.
- ROA: none5
- Route object: none6
- Route object: RIR1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 104.251.115.0/24 | No ROA covers it. Add a ROA for AS14397, maxLength 24. |
| Route object: none | 104.251.115.0/24 | No route object for it. A route object for 104.251.114.0/23 with origin AS14397 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14397 in the RIR database for the space. |
| ROA: none | 104.251.116.0/24 | No ROA covers it. Add a ROA for AS14397, maxLength 24. |
| Route object: none | 104.251.116.0/24 | Route objects for it name AS20303. Add a route object with origin AS14397 in the RIR database for the space. |
| ROA: none | 104.251.121.0/24 | No ROA covers it. Add a ROA for AS14397, maxLength 24. |
| Route object: none | 104.251.121.0/24 | No route object for it. Add a route object with origin AS14397 in the RIR database for the space. |
| ROA: none | 192.55.95.0/24 | No ROA covers it. Add a ROA for AS14397, maxLength 24. |
| Route object: RIR | 192.55.95.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 104.251.117.0/24 | No ROA covers it. Add a ROA for AS14397, maxLength 24. |
| Route object: none | 104.251.124.0/24 | No route object for it. A route object for 104.251.124.0/22 with origin AS14397 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14397 in the RIR database for the space. |
| Route object: none | 104.251.125.0/24 | No route object for it. A route object for 104.251.124.0/22 with origin AS14397 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14397 in the RIR database for the space. |
| Route object: none | 104.251.126.0/24 | No route object for it. A route object for 104.251.124.0/22 with origin AS14397 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14397 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS14397 whose prefix no peer sees AS14397 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 65.49.128.0/23 | ARIN | Valid |
| 65.49.149.0/24 | ARIN | Valid |
| 104.251.114.0/23 | ARIN | No ROA |
| 104.251.124.0/22 | ARIN | Valid |
| 2605:c180::/36 | 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.