Announced routes
Every prefix a peer of the route collectors sees with origin AS262934, 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.
| 168.227.144.0/24 | Valid | Nonecovered by 168.227.144.0/22 | 4 1%low visibility |
| 168.227.145.0/24 | Valid | Nonecovered by 168.227.144.0/22 | 4 1%low visibility |
| 168.227.146.0/24 | Valid | Nonecovered by 168.227.144.0/22 | 4 1%low visibility |
| 168.227.147.0/24 | Valid | Nonecovered by 168.227.144.0/22 | 4 1%low visibility |
| 191.102.248.0/24 | Valid | Nonecovered by 191.102.248.0/21 | 4 1%low visibility |
| 191.102.249.0/24 | Valid | Nonecovered by 191.102.248.0/21 | 4 1%low visibility |
| 191.102.250.0/24 | Valid | Nonecovered by 191.102.248.0/21 | 4 1%low visibility |
| 191.102.251.0/24 | Valid | Nonecovered by 191.102.248.0/21 | 4 1%low visibility |
| 191.102.252.0/24 | Valid | Nonecovered by 191.102.248.0/21 | 4 1%low visibility |
| 191.102.253.0/24 | Valid | Nonecovered by 191.102.248.0/21 | 4 1%low visibility |
| 191.102.254.0/24 | Valid | Nonecovered by 191.102.248.0/21 | 4 1%low visibility |
| 191.102.255.0/24 | Valid | Nonecovered by 191.102.248.0/21 | 4 1%low visibility |
| 168.227.144.0/22 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 191.102.248.0/21 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 2803:fa80::/32 | Valid | RIR databaseLACNIC, RADB | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS262934: AS262934:AS-PEERS. 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 (AS262934 isn't in the set, or no route object for AS262934 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 | AS262934 in it | Not covered |
|---|---|---|---|---|---|
| AS262934:AS-PEERS | LACNIC | 1 | 1 | No | 15 |
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 13 are in fix.csv.
- Route object: none12
- AS-SET: own ASN1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 168.227.144.0/24 | No route object for it. A route object for 168.227.144.0/22 with origin AS262934 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262934 in the RIR database for the space. |
| Route object: none | 168.227.145.0/24 | No route object for it. A route object for 168.227.144.0/22 with origin AS262934 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262934 in the RIR database for the space. |
| Route object: none | 168.227.146.0/24 | No route object for it. A route object for 168.227.144.0/22 with origin AS262934 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262934 in the RIR database for the space. |
| Route object: none | 168.227.147.0/24 | No route object for it. A route object for 168.227.144.0/22 with origin AS262934 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262934 in the RIR database for the space. |
| Route object: none | 191.102.248.0/24 | No route object for it. A route object for 191.102.248.0/21 with origin AS262934 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262934 in the RIR database for the space. |
| Route object: none | 191.102.249.0/24 | No route object for it. A route object for 191.102.248.0/21 with origin AS262934 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262934 in the RIR database for the space. |
| Route object: none | 191.102.250.0/24 | No route object for it. A route object for 191.102.248.0/21 with origin AS262934 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262934 in the RIR database for the space. |
| Route object: none | 191.102.251.0/24 | No route object for it. A route object for 191.102.248.0/21 with origin AS262934 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262934 in the RIR database for the space. |
| Route object: none | 191.102.252.0/24 | No route object for it. A route object for 191.102.248.0/21 with origin AS262934 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262934 in the RIR database for the space. |
| Route object: none | 191.102.253.0/24 | No route object for it. A route object for 191.102.248.0/21 with origin AS262934 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262934 in the RIR database for the space. |
| Route object: none | 191.102.254.0/24 | No route object for it. A route object for 191.102.248.0/21 with origin AS262934 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262934 in the RIR database for the space. |
| Route object: none | 191.102.255.0/24 | No route object for it. A route object for 191.102.248.0/21 with origin AS262934 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262934 in the RIR database for the space. |
| AS-SET: own ASN | AS262934:AS-PEERS | AS262934 isn't in AS262934:AS-PEERS (LACNIC) once expanded. Add AS262934 to it. |
Route objects not announced
Every route object with origin AS262934 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.