Network · data from 2026-11-12
AS262175 AS262175 - Telefonica Moviles Argentina S.A. (Movistar Argentina)
Registry name: AS262175 - Telefonica Moviles Argentina S.A. (Movistar Argentina), AR · not in PeeringDB
17IPv4 routes
100.0% RPKI valid · 29.4% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
12 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS262175, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS262175, 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.
| 201.251.182.0/24 | Valid | Nonecovered by 201.251.182.0/23 | 671 100% |
| 201.251.183.0/24 | Valid | Nonecovered by 201.251.182.0/23 | 671 100% |
| 201.251.184.0/24 | Valid | Nonecovered by 201.251.184.0/23 | 671 100% |
| 201.251.185.0/24 | Valid | Nonecovered by 201.251.184.0/23 | 671 100% |
| 200.81.36.0/24 | Valid | Nonecovered by 200.81.36.0/23 | 670 100% |
| 200.81.37.0/24 | Valid | Nonecovered by 200.81.36.0/23 | 670 100% |
| 200.81.42.0/24 | Valid | Nonecovered by 200.81.42.0/23 | 670 100% |
| 200.81.43.0/24 | Valid | Nonecovered by 200.81.42.0/23 | 670 100% |
| 200.106.240.0/24 | Valid | Nonecovered by 200.106.240.0/22 | 670 100% |
| 200.106.241.0/24 | Valid | Nonecovered by 200.106.240.0/22 | 670 100% |
| 200.106.242.0/24 | Valid | Nonecovered by 200.106.240.0/22 | 670 100% |
| 200.106.243.0/24 | Valid | Nonecovered by 200.106.240.0/22 | 670 100% |
| 201.251.182.0/23 | Valid | RIR databaseLACNIC | 671 100% |
| 201.251.184.0/23 | Valid | RIR databaseLACNIC | 671 100% |
| 200.81.36.0/23 | Valid | RIR databaseLACNIC | 670 100% |
| 200.81.42.0/23 | Valid | RIR databaseLACNIC | 670 100% |
| 200.106.240.0/22 | Valid | RIR databaseLACNIC | 670 100% |
AS-SET
AS262175 isn't in PeeringDB, where networks name their AS-SET.
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 12 are in fix.csv.
- Route object: none12
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 201.251.182.0/24 | No route object for it. A route object for 201.251.182.0/23 with origin AS262175 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262175 in the RIR database for the space. |
| Route object: none | 201.251.183.0/24 | No route object for it. A route object for 201.251.182.0/23 with origin AS262175 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262175 in the RIR database for the space. |
| Route object: none | 201.251.184.0/24 | No route object for it. A route object for 201.251.184.0/23 with origin AS262175 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262175 in the RIR database for the space. |
| Route object: none | 201.251.185.0/24 | No route object for it. A route object for 201.251.184.0/23 with origin AS262175 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262175 in the RIR database for the space. |
| Route object: none | 200.81.36.0/24 | No route object for it. A route object for 200.81.36.0/23 with origin AS262175 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262175 in the RIR database for the space. |
| Route object: none | 200.81.37.0/24 | No route object for it. A route object for 200.81.36.0/23 with origin AS262175 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262175 in the RIR database for the space. |
| Route object: none | 200.81.42.0/24 | No route object for it. A route object for 200.81.42.0/23 with origin AS262175 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262175 in the RIR database for the space. |
| Route object: none | 200.81.43.0/24 | No route object for it. A route object for 200.81.42.0/23 with origin AS262175 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262175 in the RIR database for the space. |
| Route object: none | 200.106.240.0/24 | No route object for it. A route object for 200.106.240.0/22 with origin AS262175 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262175 in the RIR database for the space. |
| Route object: none | 200.106.241.0/24 | No route object for it. A route object for 200.106.240.0/22 with origin AS262175 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262175 in the RIR database for the space. |
| Route object: none | 200.106.242.0/24 | No route object for it. A route object for 200.106.240.0/22 with origin AS262175 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262175 in the RIR database for the space. |
| Route object: none | 200.106.243.0/24 | No route object for it. A route object for 200.106.240.0/22 with origin AS262175 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262175 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS262175 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.