Network · data from 2026-11-12
AS25795 ARP Networks, Inc.
Registry name: ARPNET - ARP NETWORKS, INC., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS25795, 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.
| 185.139.32.0/23 | Valid | Nonecovered by 185.139.32.0/22 | 673 100% |
| 185.139.32.0/24 | Valid | Nonecovered by 185.139.32.0/22 | 673 100% |
| 185.139.33.0/24 | Valid | Nonecovered by 185.139.32.0/22 | 673 100% |
| 2607:f2f8::/32 | Valid | Other IRR onlyALTDB | 636 100% |
| 174.136.96.0/20 | Valid | RIR databaseALTDB, ARIN | 673 100% |
| 206.125.168.0/22 | Valid | RIR databaseARIN | 673 100% |
| 206.125.172.0/24 | Valid | RIR databaseARIN | 673 100% |
| 206.125.173.0/24 | Valid | RIR databaseARIN | 673 100% |
| 206.125.174.0/24 | Valid | RIR databaseARIN | 673 100% |
| 206.162.240.0/23 | Valid | RIR databaseARIN | 673 100% |
| 206.162.242.0/24 | Valid | RIR databaseARIN | 673 100% |
| 208.79.88.0/21 | Valid | RIR databaseALTDB, ARIN | 673 100% |
| 2a07:12c5::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a07:12c0::/29 | Valid | RIR databaseALTDB, RIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS25795: AS25795. 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 (AS25795 isn't in the set, or no route object for AS25795 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 | AS25795 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS25795 | A single AS number, not a set: AS25795 (this network), 17 route objects. | |||||
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 10 are in fix.csv.
- Route object: none3
- Route object: RIR1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.139.32.0/23 | No route object for it. A route object for 185.139.32.0/22 with origin AS25795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25795 in the RIR database for the space. |
| Route object: none | 185.139.32.0/24 | No route object for it. A route object for 185.139.32.0/22 with origin AS25795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25795 in the RIR database for the space. |
| Route object: none | 185.139.33.0/24 | No route object for it. A route object for 185.139.32.0/22 with origin AS25795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25795 in the RIR database for the space. |
| Route object: RIR | 2607:f2f8::/32 | Route object only in ALTDB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS25795 whose prefix no peer sees AS25795 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 44.135.193.0/24 | ALTDB | No ROA |
| 185.139.32.0/22 | ALTDB | No ROA |
| 192.88.99.0/24 | ALTDB | No ROA |
| 206.125.168.0/21 | ALTDB | No ROA |
| 206.162.240.0/20 | ALTDB, RADB | No ROA |
| 2a0c:7f80::/30 | ALTDB | No ROA |
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.