Network · data from 2026-11-12
AS398391 Perimeter 81 (AS398391)
Registry name: PERIMETER-81-LLC - Perimeter 81 LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS398391, 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.226.128.0/24 | Valid | RIR databaseARIN | 673 100% |
| 64.226.129.0/24 | Valid | RIR databaseARIN | 673 100% |
| 64.226.134.0/24 | Valid | RIR databaseARIN | 673 100% |
| 64.226.137.0/24 | Valid | RIR databaseARIN | 673 100% |
| 64.226.139.0/24 | Valid | RIR databaseARIN | 673 100% |
| 64.226.140.0/24 | Valid | RIR databaseARIN | 673 100% |
| 64.226.142.0/24 | Valid | RIR databaseARIN | 673 100% |
| 64.227.192.0/24 | Valid | RIR databaseARIN | 673 100% |
| 64.227.194.0/24 | Valid | RIR databaseARIN | 673 100% |
| 64.227.195.0/24 | Valid | RIR databaseARIN | 673 100% |
| 64.227.198.0/24 | Valid | RIR databaseARIN | 673 100% |
| 64.227.199.0/24 | Valid | RIR databaseARIN | 673 100% |
| 64.227.200.0/24 | Valid | RIR databaseARIN | 673 100% |
| 64.227.203.0/24 | Valid | RIR databaseARIN | 673 100% |
| 64.227.205.0/24 | Valid | RIR databaseARIN | 673 100% |
| 64.227.206.0/24 | Valid | RIR databaseARIN | 673 100% |
| 131.226.32.0/24 | Valid | RIR databaseARIN | 673 100% |
| 131.226.33.0/24 | Valid | RIR databaseARIN | 673 100% |
| 131.226.34.0/24 | Valid | RIR databaseARIN | 673 100% |
| 131.226.36.0/24 | Valid | RIR databaseARIN | 673 100% |
| 131.226.37.0/24 | Valid | RIR databaseARIN | 673 100% |
| 131.226.42.0/24 | Valid | RIR databaseARIN | 673 100% |
| 131.226.43.0/24 | Valid | RIR databaseARIN | 673 100% |
| 131.226.44.0/24 | Valid | RIR databaseARIN | 673 100% |
| 131.226.45.0/24 | Valid | RIR databaseARIN | 673 100% |
| 131.226.46.0/24 | Valid | RIR databaseARIN | 673 100% |
| 64.226.133.0/24 | Valid | RIR databaseARIN | 672 100% |
| 64.227.197.0/24 | Valid | RIR databaseARIN | 672 100% |
| 64.227.201.0/24 | Valid | RIR databaseARIN | 672 100% |
| 131.226.35.0/24 | Valid | RIR databaseARIN | 672 100% |
| 64.226.130.0/24 | Valid | RIR databaseARIN | 671 100% |
| 64.226.131.0/24 | Valid | RIR databaseARIN | 671 100% |
| 64.226.132.0/24 | Valid | RIR databaseARIN | 671 100% |
| 64.226.135.0/24 | Valid | RIR databaseARIN | 671 100% |
| 64.226.136.0/24 | Valid | RIR databaseARIN | 671 100% |
| 64.226.138.0/24 | Valid | RIR databaseARIN | 671 100% |
| 64.226.141.0/24 | Valid | RIR databaseARIN | 671 100% |
| 64.226.143.0/24 | Valid | RIR databaseARIN | 671 100% |
| 64.227.193.0/24 | Valid | RIR databaseARIN | 671 100% |
| 64.227.196.0/24 | Valid | RIR databaseARIN | 671 100% |
| 64.227.202.0/24 | Valid | RIR databaseARIN | 671 100% |
| 64.227.204.0/24 | Valid | RIR databaseARIN | 671 100% |
| 64.227.207.0/24 | Valid | RIR databaseARIN | 671 100% |
| 131.226.38.0/24 | Valid | RIR databaseARIN | 671 100% |
| 131.226.39.0/24 | Valid | RIR databaseARIN | 671 100% |
| 131.226.47.0/24 | Valid | RIR databaseARIN | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS398391: AS398391: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 (AS398391 isn't in the set, or no route object for AS398391 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 | AS398391 in it | Not covered |
|---|---|---|---|---|---|
| AS398391:AS-ALL | ARIN | 1 | 1 | Yes | 0 |
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS398391 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.