bgpreport

Network · data from 2026-11-12

AS28000 LACNIC Montevideo

Registry name: AS28000 - LACNIC - Latin American and Caribbean IP address, UY · PeeringDB

14IPv4 routes 100.0% RPKI valid · 42.9% with a route object
5IPv6 routes 100.0% RPKI valid · 60.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 10 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS28000, seen from no peer

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% 67
168.121.187.0/24 Valid Nonecovered by 168.121.184.0/22 671 100% 67
179.0.159.0/24 Valid Nonecovered by 179.0.156.0/22 671 100% 67
200.10.62.0/24 Valid Nonecovered by 200.10.62.0/23 670 100% 67
2801:1b8::/48 Valid Nonecovered by 2801:1b8::/44 636 100% 67
2801:1b8::/46 Valid Nonecovered by 2801:1b8::/44 634 100% 68
168.121.184.0/24 Valid Nonecovered by 168.121.184.0/22 1 0%low visibility 1
168.121.185.0/24 Valid Nonecovered by 168.121.184.0/22 1 0%low visibility 1
179.0.157.0/24 Valid Nonecovered by 179.0.156.0/22 1 0%low visibility 1
200.7.84.0/24 Valid Nonecovered by 200.7.84.0/23 1 0%low visibility 1
2801:1b8:4::/46 Valid Other IRR onlyRADB 0 0%low visibility 1
168.121.184.0/22 Valid RIR databaseLACNIC, RADB, RIPE-NONAUTH 673 100% 66
179.0.156.0/22 Valid RIR databaseLACNIC, RADB, RIPE-NONAUTH 672 100% 66
200.7.84.0/23 Valid RIR databaseLACNIC, RADB, RIPE-NONAUTH 672 100% 66
200.7.87.0/24 Valid RIR databaseLACNIC, RIPE-NONAUTH 672 100% 66
200.10.62.0/23 Valid RIR databaseLACNIC, RADB, RIPE-NONAUTH 672 100% 66
200.10.61.0/24 Valid RIR databaseLACNIC, RADB 671 100% 66
2801:1b8::/44 Valid RIR databaseLACNIC, RADB 636 100% 67
2001:13c7:7001::/48 Valid RIR databaseLACNIC, NTTCOM, RADB, RIPE-NONAUTH 634 100% 68

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
ChangePrefix or setDetailFull-table peers
Route object: none168.121.186.0/24No 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.671 of 673
Route object: none168.121.187.0/24No 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.671 of 673
Route object: none179.0.159.0/24No 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.671 of 673
Route object: none200.10.62.0/24No 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.670 of 673
Route object: none2801:1b8::/48No 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.636 of 636
Route object: none2801:1b8::/46No 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.634 of 636
Route object: none168.121.184.0/24No 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.1 of 673
Route object: none168.121.185.0/24No 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.1 of 673
Route object: none179.0.157.0/24No 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.1 of 673
Route object: none200.7.84.0/24No 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.1 of 673
Route object: RIR2801:1b8:4::/46Route object only in RADB. Add it in the RIR database for the space.0 of 636

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/22LACNIC, RADB, RIPE-NONAUTHValid
200.0.88.0/22RADBNo ROA
200.7.84.0/22RADBNo ROA
200.10.60.0/22RADBNo ROA
2001:13c7:7010::/46LACNIC, RADB, RIPE-NONAUTHValid
2001:13c7:7020::/44RADBNo ROA
2801:17:7800::/48LACNICValid
2801:165::/56LACNICValid

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.