Network · data from 2026-11-12
AS63297 Pacific Servers, Inc.
Registry name: PACIFIC-SERVERS - Pacific Servers Inc., CA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS63297, 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.
| 199.60.63.0/24 | No ROA | None | 673 100% |
| 44.31.37.0/24 | No ROA | Other origin only | 71 11% |
| 130.51.184.0/22 | Valid | RIR databaseARIN | 670 100% |
| 192.243.214.0/23 | Valid | RIR databaseARIN | 670 100% |
| 2605:cf80::/32 | Valid | RIR databaseARIN | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS63297: AS63297:AS-ALL. 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 (AS63297 isn't in the set, or no route object for AS63297 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 | AS63297 in it | Not covered |
|---|---|---|---|---|---|
| AS63297:AS-ALL | ARIN | 1 | 1 | Yes | 2 |
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 4 are in fix.csv.
- ROA: none2
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 199.60.63.0/24 | No ROA covers it. Add a ROA for AS63297, maxLength 24. |
| Route object: none | 199.60.63.0/24 | No route object for it. Add a route object with origin AS63297 in the RIR database for the space. |
| ROA: none | 44.31.37.0/24 | No ROA covers it. Add a ROA for AS63297, maxLength 24. |
| Route object: none | 44.31.37.0/24 | Route objects for it name AS20473. Add a route object with origin AS63297 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS63297 is announced.
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.