Network · data from 2026-11-12
AS27398 Alyeska Information Technology Services
Registry name: AITSL-27398 - Alyeska Information Technology Services LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS27398, 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.
| 162.218.248.0/23 | Valid | Nonecovered by 162.218.248.0/22 | 670 100% |
| 162.218.250.0/23 | Valid | Nonecovered by 162.218.248.0/22 | 670 100% |
| 2602:fed5::/47 | Valid | Nonecovered by 2602:fed5::/36 | 634 100% |
| 2602:fed5:2::/47 | Valid | Nonecovered by 2602:fed5::/36 | 634 100% |
| 74.123.136.0/22 | Valid | RIR databaseARIN, RADB | 670 100% |
| 206.81.160.0/22 | Valid | RIR databaseARIN, RADB | 670 100% |
AS-SET
AS27398'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 11 are in fix.csv.
- Route object: none4
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 162.218.248.0/23 | No route object for it. A route object for 162.218.248.0/22 with origin AS27398 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27398 in the RIR database for the space. |
| Route object: none | 162.218.250.0/23 | No route object for it. A route object for 162.218.248.0/22 with origin AS27398 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27398 in the RIR database for the space. |
| Route object: none | 2602:fed5::/47 | No route object for it. A route object for 2602:fed5::/36 with origin AS27398 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27398 in the RIR database for the space. |
| Route object: none | 2602:fed5:2::/47 | No route object for it. A route object for 2602:fed5::/36 with origin AS27398 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27398 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS27398 whose prefix no peer sees AS27398 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 162.218.248.0/22 | ARIN, RADB | Valid |
| 162.218.250.0/24 | RADB | Valid |
| 162.218.251.0/24 | RADB | Valid |
| 206.81.160.0/23 | RADB | Valid |
| 206.81.162.0/23 | RADB | Valid |
| 2602:fed5::/36 | ARIN, RADB | Valid |
| 2602:fed5:800::/37 | RADB | 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.