Network · data from 2026-11-12
AS28111 Grupo Solunet SRL
Registry name: AS28111 - Grupo Solunet SRL, AR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS28111, 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.
| 190.0.160.0/24 | Valid | Nonecovered by 190.0.160.0/19 | 666 99% |
| 190.0.161.0/24 | Valid | Nonecovered by 190.0.160.0/19 | 666 99% |
| 190.0.163.0/24 | Valid | Nonecovered by 190.0.160.0/19 | 666 99% |
| 190.0.165.0/24 | Valid | Nonecovered by 190.0.160.0/19 | 666 99% |
| 190.0.166.0/24 | Valid | Nonecovered by 190.0.160.0/19 | 666 99% |
| 190.0.168.0/22 | Valid | Nonecovered by 190.0.160.0/19 | 666 99% |
| 190.0.172.0/22 | Valid | Nonecovered by 190.0.160.0/19 | 666 99% |
| 190.0.176.0/22 | Valid | Nonecovered by 190.0.160.0/19 | 666 99% |
| 190.0.180.0/22 | Valid | Nonecovered by 190.0.160.0/19 | 666 99% |
| 190.0.184.0/22 | Valid | Nonecovered by 190.0.160.0/19 | 666 99% |
| 190.0.188.0/22 | Valid | Nonecovered by 190.0.160.0/19 | 666 99% |
| 190.112.0.0/22 | Valid | Nonecovered by 190.112.0.0/19 | 666 99% |
| 190.112.4.0/22 | Valid | Nonecovered by 190.112.0.0/19 | 666 99% |
| 190.112.8.0/22 | Valid | Nonecovered by 190.112.0.0/19 | 666 99% |
| 190.112.12.0/22 | Valid | Nonecovered by 190.112.0.0/19 | 666 99% |
| 190.112.16.0/22 | Valid | Nonecovered by 190.112.0.0/19 | 666 99% |
| 190.112.20.0/22 | Valid | Nonecovered by 190.112.0.0/19 | 666 99% |
| 190.112.24.0/22 | Valid | Nonecovered by 190.112.0.0/19 | 666 99% |
| 190.112.28.0/22 | Valid | Nonecovered by 190.112.0.0/19 | 666 99% |
AS-SET
PeeringDB's irr_as_set for AS28111: AS28111:AS-SOLUNET. 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 (AS28111 isn't in the set, or no route object for AS28111 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 | AS28111 in it | Not covered |
|---|---|---|---|---|---|
| AS28111:AS-SOLUNET | LACNIC | 19 | 5 | 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 22 are in fix.csv.
- Route object: none19
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 190.0.160.0/24 | No route object for it. A route object for 190.0.160.0/19 with origin AS28111 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28111 in the RIR database for the space. |
| Route object: none | 190.0.161.0/24 | No route object for it. A route object for 190.0.160.0/19 with origin AS28111 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28111 in the RIR database for the space. |
| Route object: none | 190.0.163.0/24 | No route object for it. A route object for 190.0.160.0/19 with origin AS28111 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28111 in the RIR database for the space. |
| Route object: none | 190.0.165.0/24 | No route object for it. A route object for 190.0.160.0/19 with origin AS28111 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28111 in the RIR database for the space. |
| Route object: none | 190.0.166.0/24 | No route object for it. A route object for 190.0.160.0/19 with origin AS28111 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28111 in the RIR database for the space. |
| Route object: none | 190.0.168.0/22 | No route object for it. A route object for 190.0.160.0/19 with origin AS28111 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28111 in the RIR database for the space. |
| Route object: none | 190.0.172.0/22 | No route object for it. A route object for 190.0.160.0/19 with origin AS28111 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28111 in the RIR database for the space. |
| Route object: none | 190.0.176.0/22 | No route object for it. A route object for 190.0.160.0/19 with origin AS28111 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28111 in the RIR database for the space. |
| Route object: none | 190.0.180.0/22 | No route object for it. A route object for 190.0.160.0/19 with origin AS28111 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28111 in the RIR database for the space. |
| Route object: none | 190.0.184.0/22 | No route object for it. A route object for 190.0.160.0/19 with origin AS28111 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28111 in the RIR database for the space. |
| Route object: none | 190.0.188.0/22 | No route object for it. A route object for 190.0.160.0/19 with origin AS28111 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28111 in the RIR database for the space. |
| Route object: none | 190.112.0.0/22 | No route object for it. A route object for 190.112.0.0/19 with origin AS28111 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28111 in the RIR database for the space. |
| Route object: none | 190.112.4.0/22 | No route object for it. A route object for 190.112.0.0/19 with origin AS28111 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28111 in the RIR database for the space. |
| Route object: none | 190.112.8.0/22 | No route object for it. A route object for 190.112.0.0/19 with origin AS28111 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28111 in the RIR database for the space. |
| Route object: none | 190.112.12.0/22 | No route object for it. A route object for 190.112.0.0/19 with origin AS28111 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28111 in the RIR database for the space. |
| Route object: none | 190.112.16.0/22 | No route object for it. A route object for 190.112.0.0/19 with origin AS28111 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28111 in the RIR database for the space. |
| Route object: none | 190.112.20.0/22 | No route object for it. A route object for 190.112.0.0/19 with origin AS28111 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28111 in the RIR database for the space. |
| Route object: none | 190.112.24.0/22 | No route object for it. A route object for 190.112.0.0/19 with origin AS28111 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28111 in the RIR database for the space. |
| Route object: none | 190.112.28.0/22 | No route object for it. A route object for 190.112.0.0/19 with origin AS28111 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28111 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS28111 whose prefix no peer sees AS28111 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 190.0.160.0/19 | LACNIC | Valid |
| 190.112.0.0/19 | LACNIC | Valid |
| 2803:1e80::/32 | LACNIC | 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.