Network · data from 2026-11-12
AS52255 Grupo Servicios Junin
Registry name: AS52255 - Grupo Servicios Junin S.A., AR · PeeringDB
28IPv4 routes
100.0% RPKI valid · 14.3% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
24 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS52255, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS52255, 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.
| 186.0.168.0/24 | Valid | Nonecovered by 186.0.160.0/20 | 671 100% |
| 186.0.169.0/24 | Valid | Nonecovered by 186.0.160.0/20 | 671 100% |
| 186.0.170.0/24 | Valid | Nonecovered by 186.0.160.0/20 | 671 100% |
| 186.0.171.0/24 | Valid | Nonecovered by 186.0.160.0/20 | 671 100% |
| 186.0.172.0/24 | Valid | Nonecovered by 186.0.160.0/20 | 671 100% |
| 186.0.173.0/24 | Valid | Nonecovered by 186.0.160.0/20 | 671 100% |
| 186.0.174.0/24 | Valid | Nonecovered by 186.0.160.0/20 | 671 100% |
| 201.159.56.0/24 | Valid | Nonecovered by 201.159.56.0/21 | 671 100% |
| 201.159.57.0/24 | Valid | Nonecovered by 201.159.56.0/21 | 671 100% |
| 201.159.58.0/24 | Valid | Nonecovered by 201.159.56.0/21 | 671 100% |
| 201.159.59.0/24 | Valid | Nonecovered by 201.159.56.0/21 | 671 100% |
| 201.159.60.0/24 | Valid | Nonecovered by 201.159.56.0/21 | 671 100% |
| 186.0.160.0/24 | Valid | Nonecovered by 186.0.160.0/20 | 670 100% |
| 186.0.161.0/24 | Valid | Nonecovered by 186.0.160.0/20 | 670 100% |
| 186.0.162.0/24 | Valid | Nonecovered by 186.0.160.0/20 | 670 100% |
| 186.0.163.0/24 | Valid | Nonecovered by 186.0.160.0/20 | 670 100% |
| 186.0.164.0/24 | Valid | Nonecovered by 186.0.160.0/20 | 670 100% |
| 186.0.165.0/24 | Valid | Nonecovered by 186.0.160.0/20 | 670 100% |
| 186.0.166.0/24 | Valid | Nonecovered by 186.0.160.0/20 | 670 100% |
| 186.0.167.0/24 | Valid | Nonecovered by 186.0.160.0/20 | 670 100% |
| 201.159.61.0/24 | Valid | Nonecovered by 201.159.56.0/21 | 670 100% |
| 201.159.62.0/24 | Valid | Nonecovered by 201.159.56.0/21 | 670 100% |
| 201.159.63.0/24 | Valid | Nonecovered by 201.159.56.0/21 | 670 100% |
| 186.0.175.0/24 | Valid | Nonecovered by 186.0.160.0/20 | 8 1%low visibility |
| 186.0.160.0/20 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 201.159.56.0/21 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 201.234.19.0/24 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 201.234.101.0/24 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 2803:f100::/32 | Valid | RIR databaseLACNIC, RADB | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS52255: AS52255:AS-CUSTOMERS. 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 (AS52255 isn't in the set, or no route object for AS52255 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 | AS52255 in it | Not covered |
|---|---|---|---|---|---|
| AS52255:AS-CUSTOMERS | LACNIC | 9 | 1 | No | 29 |
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 25 are in fix.csv.
- Route object: none24
- AS-SET: own ASN1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 186.0.168.0/24 | No route object for it. A route object for 186.0.160.0/20 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| Route object: none | 186.0.169.0/24 | No route object for it. A route object for 186.0.160.0/20 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| Route object: none | 186.0.170.0/24 | No route object for it. A route object for 186.0.160.0/20 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| Route object: none | 186.0.171.0/24 | No route object for it. A route object for 186.0.160.0/20 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| Route object: none | 186.0.172.0/24 | No route object for it. A route object for 186.0.160.0/20 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| Route object: none | 186.0.173.0/24 | No route object for it. A route object for 186.0.160.0/20 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| Route object: none | 186.0.174.0/24 | No route object for it. A route object for 186.0.160.0/20 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| Route object: none | 201.159.56.0/24 | No route object for it. A route object for 201.159.56.0/21 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| Route object: none | 201.159.57.0/24 | No route object for it. A route object for 201.159.56.0/21 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| Route object: none | 201.159.58.0/24 | No route object for it. A route object for 201.159.56.0/21 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| Route object: none | 201.159.59.0/24 | No route object for it. A route object for 201.159.56.0/21 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| Route object: none | 201.159.60.0/24 | No route object for it. A route object for 201.159.56.0/21 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| Route object: none | 186.0.160.0/24 | No route object for it. A route object for 186.0.160.0/20 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| Route object: none | 186.0.161.0/24 | No route object for it. A route object for 186.0.160.0/20 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| Route object: none | 186.0.162.0/24 | No route object for it. A route object for 186.0.160.0/20 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| Route object: none | 186.0.163.0/24 | No route object for it. A route object for 186.0.160.0/20 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| Route object: none | 186.0.164.0/24 | No route object for it. A route object for 186.0.160.0/20 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| Route object: none | 186.0.165.0/24 | No route object for it. A route object for 186.0.160.0/20 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| Route object: none | 186.0.166.0/24 | No route object for it. A route object for 186.0.160.0/20 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| Route object: none | 186.0.167.0/24 | No route object for it. A route object for 186.0.160.0/20 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| Route object: none | 201.159.61.0/24 | No route object for it. A route object for 201.159.56.0/21 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| Route object: none | 201.159.62.0/24 | No route object for it. A route object for 201.159.56.0/21 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| Route object: none | 201.159.63.0/24 | No route object for it. A route object for 201.159.56.0/21 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| Route object: none | 186.0.175.0/24 | No route object for it. A route object for 186.0.160.0/20 with origin AS52255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52255 in the RIR database for the space. |
| AS-SET: own ASN | AS52255:AS-CUSTOMERS | AS52255 isn't in AS52255:AS-CUSTOMERS (LACNIC) once expanded. Add AS52255 to it. |
Route objects not announced
Every route object with origin AS52255 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.