Network · data from 2026-11-12
AS263769 ByteSolution
Registry name: AS263769 - ByteSolution S.A. (WispSolution Internet), AR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263769, 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.90.129.0/24 | Valid | Nonecovered by 168.90.128.0/22 | 4 1%low visibility |
| 168.90.130.0/24 | Valid | Nonecovered by 168.90.128.0/22 | 4 1%low visibility |
| 168.90.131.0/24 | Valid | Nonecovered by 168.90.128.0/22 | 4 1%low visibility |
| 170.238.20.0/24 | Valid | Nonecovered by 170.238.20.0/22 | 4 1%low visibility |
| 170.238.21.0/24 | Valid | Nonecovered by 170.238.20.0/22 | 4 1%low visibility |
| 170.238.22.0/24 | Valid | Nonecovered by 170.238.20.0/22 | 4 1%low visibility |
| 170.238.23.0/24 | Valid | Nonecovered by 170.238.20.0/22 | 4 1%low visibility |
| 179.60.248.0/24 | Valid | Nonecovered by 179.60.248.0/21 | 4 1%low visibility |
| 179.60.249.0/24 | Valid | Nonecovered by 179.60.248.0/21 | 4 1%low visibility |
| 179.60.250.0/24 | Valid | Nonecovered by 179.60.248.0/21 | 4 1%low visibility |
| 179.60.251.0/24 | Valid | Nonecovered by 179.60.248.0/21 | 4 1%low visibility |
| 179.60.252.0/24 | Valid | Nonecovered by 179.60.248.0/21 | 4 1%low visibility |
| 179.60.253.0/24 | Valid | Nonecovered by 179.60.248.0/21 | 4 1%low visibility |
| 179.60.254.0/24 | Valid | Nonecovered by 179.60.248.0/21 | 4 1%low visibility |
| 179.60.255.0/24 | Valid | Nonecovered by 179.60.248.0/21 | 4 1%low visibility |
| 168.90.128.0/24 | Valid | Other IRR onlyRADB | 4 1%low visibility |
| 168.90.128.0/22 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 170.238.20.0/22 | Valid | RIR databaseLACNIC | 672 100% |
| 179.60.248.0/21 | Valid | RIR databaseLACNIC | 672 100% |
| 2803:7880::/32 | Valid | RIR databaseLACNIC, RADB | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS263769: AS263769:AS-BYTESOLUTION. 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 (AS263769 isn't in the set, or no route object for AS263769 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 | AS263769 in it | Not covered |
|---|---|---|---|---|---|
| AS263769:AS-BYTESOLUTION | LACNIC | 11 | 1 | No | 20 |
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 17 are in fix.csv.
- Route object: none15
- Route object: RIR1
- AS-SET: own ASN1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 168.90.129.0/24 | No route object for it. A route object for 168.90.128.0/22 with origin AS263769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263769 in the RIR database for the space. |
| Route object: none | 168.90.130.0/24 | No route object for it. A route object for 168.90.128.0/22 with origin AS263769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263769 in the RIR database for the space. |
| Route object: none | 168.90.131.0/24 | No route object for it. A route object for 168.90.128.0/22 with origin AS263769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263769 in the RIR database for the space. |
| Route object: none | 170.238.20.0/24 | No route object for it. A route object for 170.238.20.0/22 with origin AS263769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263769 in the RIR database for the space. |
| Route object: none | 170.238.21.0/24 | No route object for it. A route object for 170.238.20.0/22 with origin AS263769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263769 in the RIR database for the space. |
| Route object: none | 170.238.22.0/24 | No route object for it. A route object for 170.238.20.0/22 with origin AS263769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263769 in the RIR database for the space. |
| Route object: none | 170.238.23.0/24 | No route object for it. A route object for 170.238.20.0/22 with origin AS263769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263769 in the RIR database for the space. |
| Route object: none | 179.60.248.0/24 | No route object for it. A route object for 179.60.248.0/21 with origin AS263769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263769 in the RIR database for the space. |
| Route object: none | 179.60.249.0/24 | No route object for it. A route object for 179.60.248.0/21 with origin AS263769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263769 in the RIR database for the space. |
| Route object: none | 179.60.250.0/24 | No route object for it. A route object for 179.60.248.0/21 with origin AS263769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263769 in the RIR database for the space. |
| Route object: none | 179.60.251.0/24 | No route object for it. A route object for 179.60.248.0/21 with origin AS263769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263769 in the RIR database for the space. |
| Route object: none | 179.60.252.0/24 | No route object for it. A route object for 179.60.248.0/21 with origin AS263769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263769 in the RIR database for the space. |
| Route object: none | 179.60.253.0/24 | No route object for it. A route object for 179.60.248.0/21 with origin AS263769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263769 in the RIR database for the space. |
| Route object: none | 179.60.254.0/24 | No route object for it. A route object for 179.60.248.0/21 with origin AS263769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263769 in the RIR database for the space. |
| Route object: none | 179.60.255.0/24 | No route object for it. A route object for 179.60.248.0/21 with origin AS263769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263769 in the RIR database for the space. |
| Route object: RIR | 168.90.128.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: own ASN | AS263769:AS-BYTESOLUTION | AS263769 isn't in AS263769:AS-BYTESOLUTION (LACNIC) once expanded. Add AS263769 to it. |
Route objects not announced
Every route object with origin AS263769 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.