Network · data from 2026-11-12
AS19180 Americatel Perú
Registry name: AS19180 - AMERICATEL PERU S.A., PE · PeeringDB
47IPv4 routes
100.0% RPKI valid · 27.7% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
34 with no route object for this origin
3Low visibility
seen by under 10% of full-table peers
43Route objects not announced
registered with origin AS19180, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS19180, 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.
| 148.102.0.0/20 | Valid | Nonecovered by 148.102.0.0/17 | 671 100% |
| 148.102.16.0/20 | Valid | Nonecovered by 148.102.0.0/17 | 671 100% |
| 148.102.32.0/20 | Valid | Nonecovered by 148.102.0.0/17 | 671 100% |
| 148.102.64.0/20 | Valid | Nonecovered by 148.102.0.0/17 | 671 100% |
| 148.102.80.0/20 | Valid | Nonecovered by 148.102.0.0/17 | 671 100% |
| 148.102.112.0/20 | Valid | Nonecovered by 148.102.0.0/17 | 671 100% |
| 190.8.128.0/20 | Valid | Nonecovered by 190.8.128.0/19 | 670 100% |
| 190.8.144.0/20 | Valid | Nonecovered by 190.8.128.0/19 | 670 100% |
| 190.187.0.0/20 | Valid | Nonecovered by 190.187.0.0/17 | 670 100% |
| 190.187.16.0/20 | Valid | Nonecovered by 190.187.0.0/17 | 670 100% |
| 190.187.32.0/20 | Valid | Nonecovered by 190.187.0.0/17 | 670 100% |
| 190.187.48.0/20 | Valid | Nonecovered by 190.187.0.0/17 | 670 100% |
| 190.187.80.0/20 | Valid | Nonecovered by 190.187.0.0/17 | 670 100% |
| 190.187.96.0/20 | Valid | Nonecovered by 190.187.0.0/17 | 670 100% |
| 190.187.112.0/20 | Valid | Nonecovered by 190.187.0.0/17 | 670 100% |
| 190.187.128.0/20 | Valid | Nonecovered by 190.187.128.0/17 | 670 100% |
| 190.187.144.0/20 | Valid | Nonecovered by 190.187.128.0/17 | 670 100% |
| 190.187.160.0/20 | Valid | Nonecovered by 190.187.128.0/17 | 670 100% |
| 190.187.176.0/20 | Valid | Nonecovered by 190.187.128.0/17 | 670 100% |
| 190.187.192.0/20 | Valid | Nonecovered by 190.187.128.0/17 | 670 100% |
| 190.187.208.0/20 | Valid | Nonecovered by 190.187.128.0/17 | 670 100% |
| 190.187.224.0/20 | Valid | Nonecovered by 190.187.128.0/17 | 670 100% |
| 190.187.240.0/20 | Valid | Nonecovered by 190.187.128.0/17 | 670 100% |
| 200.31.96.0/20 | Valid | Nonecovered by 200.31.96.0/19 | 670 100% |
| 200.110.16.0/22 | Valid | Nonecovered by 200.110.16.0/21 | 670 100% |
| 200.110.20.0/22 | Valid | Nonecovered by 200.110.16.0/21 | 670 100% |
| 148.102.48.0/20 | Valid | Other origin onlycovered by 148.102.0.0/17 | 668 99% |
| 148.102.96.0/20 | Valid | Other origin onlycovered by 148.102.0.0/17 | 668 99% |
| 148.102.71.0/24 | Valid | Other origin onlycovered by 148.102.0.0/17 | 125 19% |
| 148.102.72.0/24 | Valid | Other origin onlycovered by 148.102.0.0/17 | 125 19% |
| 148.102.73.0/24 | Valid | Other origin onlycovered by 148.102.0.0/17 | 125 19% |
| 148.102.51.0/24 | Valid | Nonecovered by 148.102.0.0/17 | 30 4%low visibility |
| 148.102.58.0/24 | Valid | Nonecovered by 148.102.0.0/17 | 30 4%low visibility |
| 190.187.196.0/24 | Valid | Nonecovered by 190.187.128.0/17 | 2 0%low visibility |
| 186.160.60.0/22 | Valid | Other IRR onlyRADB | 671 100% |
| 186.160.72.0/22 | Valid | Other IRR onlyRADB | 671 100% |
| 186.160.88.0/22 | Valid | Other IRR onlyRADB | 671 100% |
| 190.187.64.0/20 | Valid | Other IRR onlyRADB | 670 100% |
| 200.31.112.0/20 | Valid | Other IRR onlyRADB | 670 100% |
| 200.110.12.0/22 | Valid | Other IRR onlyRADB | 670 100% |
| 200.110.26.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 200.110.27.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 200.110.36.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 200.110.40.0/22 | Valid | Other IRR onlyRADB | 670 100% |
| 200.110.44.0/22 | Valid | Other IRR onlyRADB | 670 100% |
| 200.110.25.0/24 | Valid | RIR databaseLACNIC, RADB | 670 100% |
| 200.110.32.0/22 | Valid | RIR databaseLACNIC, RADB | 670 100% |
AS-SET
AS19180's PeeringDB record names no 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 88 are in fix.csv.
- Route object: none34
- Route object: RIR11
- Route object: not announced43
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 148.102.0.0/20 | No route object for it. A route object for 148.102.0.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 148.102.16.0/20 | No route object for it. A route object for 148.102.0.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 148.102.32.0/20 | No route object for it. A route object for 148.102.0.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 148.102.64.0/20 | No route object for it. A route object for 148.102.0.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 148.102.80.0/20 | No route object for it. A route object for 148.102.0.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 148.102.112.0/20 | No route object for it. A route object for 148.102.0.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 190.8.128.0/20 | No route object for it. A route object for 190.8.128.0/19 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 190.8.144.0/20 | No route object for it. A route object for 190.8.128.0/19 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 190.187.0.0/20 | No route object for it. A route object for 190.187.0.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 190.187.16.0/20 | No route object for it. A route object for 190.187.0.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 190.187.32.0/20 | No route object for it. A route object for 190.187.0.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 190.187.48.0/20 | No route object for it. A route object for 190.187.0.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 190.187.80.0/20 | No route object for it. A route object for 190.187.0.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 190.187.96.0/20 | No route object for it. A route object for 190.187.0.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 190.187.112.0/20 | No route object for it. A route object for 190.187.0.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 190.187.128.0/20 | No route object for it. A route object for 190.187.128.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 190.187.144.0/20 | No route object for it. A route object for 190.187.128.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 190.187.160.0/20 | No route object for it. A route object for 190.187.128.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 190.187.176.0/20 | No route object for it. A route object for 190.187.128.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 190.187.192.0/20 | No route object for it. A route object for 190.187.128.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 190.187.208.0/20 | No route object for it. A route object for 190.187.128.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 190.187.224.0/20 | No route object for it. A route object for 190.187.128.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 190.187.240.0/20 | No route object for it. A route object for 190.187.128.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 200.31.96.0/20 | No route object for it. A route object for 200.31.96.0/19 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 200.110.16.0/22 | No route object for it. A route object for 200.110.16.0/21 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 200.110.20.0/22 | No route object for it. A route object for 200.110.16.0/21 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 148.102.48.0/20 | Route objects for it name AS21575. A route object for 148.102.0.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 148.102.96.0/20 | Route objects for it name AS21575. A route object for 148.102.0.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 148.102.71.0/24 | Route objects for it name AS21575. A route object for 148.102.0.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 148.102.72.0/24 | Route objects for it name AS21575. A route object for 148.102.0.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 148.102.73.0/24 | Route objects for it name AS21575. A route object for 148.102.0.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 148.102.51.0/24 | No route object for it. A route object for 148.102.0.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 148.102.58.0/24 | No route object for it. A route object for 148.102.0.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: none | 190.187.196.0/24 | No route object for it. A route object for 190.187.128.0/17 with origin AS19180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19180 in the RIR database for the space. |
| Route object: RIR | 186.160.60.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.160.72.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.160.88.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.187.64.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.31.112.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.110.12.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.110.26.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.110.27.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.110.36.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.110.40.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.110.44.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS19180 whose prefix no peer sees AS19180 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 148.102.0.0/17 | LACNIC | Valid |
| 186.160.56.0/21 | LACNIC | Valid |
| 186.160.56.0/22 | RADB | Valid |
| 186.160.72.0/21 | LACNIC | Valid |
| 186.160.76.0/22 | RADB | Valid |
| 186.160.80.0/20 | LACNIC | Valid |
| 186.160.80.0/22 | RADB | Valid |
| 186.160.84.0/22 | RADB | Valid |
| 186.160.92.0/22 | RADB | Valid |
| 186.160.96.0/21 | LACNIC | Valid |
| 186.160.96.0/22 | RADB | Valid |
| 186.160.100.0/22 | RADB | Valid |
| 190.8.128.0/19 | LACNIC | Valid |
| 190.187.0.0/16 | LACNIC | Valid |
| 190.187.0.0/17 | RADB | Valid |
| 190.187.128.0/17 | RADB | Valid |
| 200.0.169.0/24 | RADB | No ROA |
| 200.31.96.0/19 | LACNIC | Valid |
| 200.31.96.0/24 | RADB | Valid |
| 200.31.97.0/24 | RADB | Valid |
| 200.31.98.0/24 | RADB | Valid |
| 200.31.99.0/24 | RADB | Valid |
| 200.31.100.0/24 | RADB | Valid |
| 200.31.101.0/24 | RADB | Valid |
| 200.31.102.0/24 | RADB | Valid |
| 200.31.103.0/24 | RADB | Valid |
| 200.31.104.0/24 | RADB | Valid |
| 200.31.105.0/24 | RADB | Valid |
| 200.31.106.0/24 | RADB | Valid |
| 200.31.107.0/24 | RADB | Valid |
| 200.31.108.0/24 | RADB | Valid |
| 200.31.109.0/24 | RADB | Valid |
| 200.31.110.0/24 | RADB | Valid |
| 200.31.111.0/24 | RADB | Valid |
| 200.110.4.0/22 | LACNIC, RADB | Valid |
| 200.110.8.0/21 | LACNIC | Valid |
| 200.110.16.0/21 | LACNIC, RADB | Valid |
| 200.110.26.0/23 | LACNIC | Valid |
| 200.110.28.0/22 | LACNIC, RADB | Valid |
| 200.110.36.0/23 | LACNIC | Valid |
| 200.110.37.0/24 | RADB | Valid |
| 200.110.40.0/21 | LACNIC | Valid |
| 2001:1380::/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.