Network · data from 2026-11-12
AS28000 LACNIC Montevideo
Registry name: AS28000 - LACNIC - Latin American and Caribbean IP address, UY · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS28000, 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.121.186.0/24 | Valid | Nonecovered by 168.121.184.0/22 | 671 100% |
| 168.121.187.0/24 | Valid | Nonecovered by 168.121.184.0/22 | 671 100% |
| 179.0.159.0/24 | Valid | Nonecovered by 179.0.156.0/22 | 671 100% |
| 200.10.62.0/24 | Valid | Nonecovered by 200.10.62.0/23 | 670 100% |
| 2801:1b8::/48 | Valid | Nonecovered by 2801:1b8::/44 | 636 100% |
| 2801:1b8::/46 | Valid | Nonecovered by 2801:1b8::/44 | 634 100% |
| 168.121.184.0/24 | Valid | Nonecovered by 168.121.184.0/22 | 1 0%low visibility |
| 168.121.185.0/24 | Valid | Nonecovered by 168.121.184.0/22 | 1 0%low visibility |
| 179.0.157.0/24 | Valid | Nonecovered by 179.0.156.0/22 | 1 0%low visibility |
| 200.7.84.0/24 | Valid | Nonecovered by 200.7.84.0/23 | 1 0%low visibility |
| 2801:1b8:4::/46 | Valid | Other IRR onlyRADB | 0 0%low visibility |
| 168.121.184.0/22 | Valid | RIR databaseLACNIC, RADB, RIPE-NONAUTH | 673 100% |
| 179.0.156.0/22 | Valid | RIR databaseLACNIC, RADB, RIPE-NONAUTH | 672 100% |
| 200.7.84.0/23 | Valid | RIR databaseLACNIC, RADB, RIPE-NONAUTH | 672 100% |
| 200.7.87.0/24 | Valid | RIR databaseLACNIC, RIPE-NONAUTH | 672 100% |
| 200.10.62.0/23 | Valid | RIR databaseLACNIC, RADB, RIPE-NONAUTH | 672 100% |
| 200.10.61.0/24 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 2801:1b8::/44 | Valid | RIR databaseLACNIC, RADB | 636 100% |
| 2001:13c7:7001::/48 | Valid | RIR databaseLACNIC, NTTCOM, RADB, RIPE-NONAUTH | 634 100% |
AS-SET
AS28000'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 19 are in fix.csv.
- Route object: none10
- Route object: RIR1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 168.121.186.0/24 | No route object for it. A route object for 168.121.184.0/22 with origin AS28000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28000 in the RIR database for the space. |
| Route object: none | 168.121.187.0/24 | No route object for it. A route object for 168.121.184.0/22 with origin AS28000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28000 in the RIR database for the space. |
| Route object: none | 179.0.159.0/24 | No route object for it. A route object for 179.0.156.0/22 with origin AS28000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28000 in the RIR database for the space. |
| Route object: none | 200.10.62.0/24 | No route object for it. A route object for 200.10.62.0/23 with origin AS28000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28000 in the RIR database for the space. |
| Route object: none | 2801:1b8::/48 | No route object for it. A route object for 2801:1b8::/44 with origin AS28000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28000 in the RIR database for the space. |
| Route object: none | 2801:1b8::/46 | No route object for it. A route object for 2801:1b8::/44 with origin AS28000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28000 in the RIR database for the space. |
| Route object: none | 168.121.184.0/24 | No route object for it. A route object for 168.121.184.0/22 with origin AS28000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28000 in the RIR database for the space. |
| Route object: none | 168.121.185.0/24 | No route object for it. A route object for 168.121.184.0/22 with origin AS28000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28000 in the RIR database for the space. |
| Route object: none | 179.0.157.0/24 | No route object for it. A route object for 179.0.156.0/22 with origin AS28000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28000 in the RIR database for the space. |
| Route object: none | 200.7.84.0/24 | No route object for it. A route object for 200.7.84.0/23 with origin AS28000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28000 in the RIR database for the space. |
| Route object: RIR | 2801:1b8:4::/46 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS28000 whose prefix no peer sees AS28000 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 170.247.168.0/22 | LACNIC, RADB, RIPE-NONAUTH | Valid |
| 200.0.88.0/22 | RADB | No ROA |
| 200.7.84.0/22 | RADB | No ROA |
| 200.10.60.0/22 | RADB | No ROA |
| 2001:13c7:7010::/46 | LACNIC, RADB, RIPE-NONAUTH | Valid |
| 2001:13c7:7020::/44 | RADB | No ROA |
| 2801:17:7800::/48 | LACNIC | Valid |
| 2801:165::/56 | 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.