Network · data from 2026-11-12
AS13880 American Century Services, LLC
Registry name: ACSL-AS1 - American Century Services, LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS13880, 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.
| 216.230.48.0/23 | Valid | Nonecovered by 216.230.48.0/20 | 673 100% |
| 216.230.62.0/23 | Valid | Nonecovered by 216.230.48.0/20 | 673 100% |
| 216.230.49.0/24 | Valid | RIR databaseARIN | 673 100% |
| 216.230.63.0/24 | Valid | RIR databaseARIN | 673 100% |
| 216.230.48.0/24 | Valid | RIR databaseARIN | 670 100% |
| 216.230.62.0/24 | Valid | RIR databaseARIN | 670 100% |
AS-SET
PeeringDB's irr_as_set for AS13880: AS-ACSL-22. 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 (AS13880 isn't in the set, or no route object for AS13880 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 | AS13880 in it | Not covered |
|---|---|---|---|---|---|
| AS-ACSL-22 | ARIN | 1 | 1 | 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 17 are in fix.csv.
- Route object: none2
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 216.230.48.0/23 | No route object for it. A route object for 216.230.48.0/20 with origin AS13880 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13880 in the RIR database for the space. |
| Route object: none | 216.230.62.0/23 | No route object for it. A route object for 216.230.48.0/20 with origin AS13880 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13880 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS13880 whose prefix no peer sees AS13880 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.57.32.0/20 | ARIN, RADB | Valid |
| 216.230.48.0/20 | RADB | Valid |
| 216.230.50.0/24 | ARIN | Valid |
| 216.230.51.0/24 | ARIN | Valid |
| 216.230.52.0/24 | ARIN | Valid |
| 216.230.53.0/24 | ARIN | Valid |
| 216.230.54.0/24 | ARIN | Valid |
| 216.230.55.0/24 | ARIN | Valid |
| 216.230.56.0/24 | ARIN | Valid |
| 216.230.57.0/24 | ARIN | Valid |
| 216.230.58.0/24 | ARIN | Valid |
| 216.230.59.0/24 | ARIN | Valid |
| 216.230.60.0/24 | ARIN | Valid |
| 216.230.61.0/24 | ARIN | Valid |
| 2620:110:7000::/44 | ARIN, 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.