Network · data from 2026-11-12
AS55064 Arista Networks
Registry name: ARISTAASN1 - Arista Networks, Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS55064, 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.
| 2620:a0:4003::/48 | Valid | Nonecovered by 2620:a0:4000::/44 | 632 99% |
| 162.210.128.0/24 | Valid | RIR databaseARIN | 673 100% |
| 162.210.129.0/24 | Valid | RIR databaseARIN | 673 100% |
| 162.210.130.0/24 | Valid | RIR databaseARIN | 673 100% |
| 162.210.131.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 74.123.29.0/24 | Valid | RIR databaseARIN | 672 100% |
| 2620:a0:4002::/48 | Valid | RIR databaseARIN | 636 100% |
| 2620:a0:4000::/48 | Valid | RIR databaseARIN | 634 100% |
| 2620:a0:4001::/48 | Valid | RIR databaseARIN | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS55064: AS-ARISTA. 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 (AS55064 isn't in the set, or no route object for AS55064 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 | AS55064 in it | Not covered |
|---|---|---|---|---|---|
| AS-ARISTA | 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 7 are in fix.csv.
- Route object: none1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2620:a0:4003::/48 | No route object for it. A route object for 2620:a0:4000::/44 with origin AS55064 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55064 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS55064 whose prefix no peer sees AS55064 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 74.123.28.0/22 | ARIN | Valid |
| 74.123.28.0/24 | ARIN | Valid |
| 74.123.30.0/24 | ARIN | Valid |
| 74.123.31.0/24 | ARIN | Valid |
| 162.210.128.0/22 | ARIN, RADB, RIPE-NONAUTH | Valid |
| 2620:a0:4000::/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.