bgpreport

Network · data from 2026-11-12

AS28001 LACNIC

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28001, 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.
200.3.12.0/24 Valid Nonecovered by 200.3.12.0/22 668 99% 67
200.3.15.0/24 Valid Nonecovered by 200.3.12.0/22 668 99% 67
200.3.13.0/24 Valid Nonecovered by 200.3.12.0/22 667 99% 67
200.3.14.0/24 Valid Other IRR onlyALTDB 668 99% 67
200.3.12.0/22 Valid RIR databaseLACNIC, RADB 668 99% 67
2001:13c7:7002::/48 Valid RIR databaseLACNIC, RADB, RIPE-NONAUTH 635 100% 67

AS-SET

AS28001'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 9 are in fix.csv.

  • Route object: none3
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none200.3.12.0/24No route object for it. A route object for 200.3.12.0/22 with origin AS28001 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28001 in the RIR database for the space.668 of 673
Route object: none200.3.15.0/24No route object for it. A route object for 200.3.12.0/22 with origin AS28001 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28001 in the RIR database for the space.668 of 673
Route object: none200.3.13.0/24No route object for it. A route object for 200.3.12.0/22 with origin AS28001 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28001 in the RIR database for the space.667 of 673
Route object: RIR200.3.14.0/24Route object only in ALTDB. Add it in the RIR database for the space.668 of 673

Route objects not announced

Route objects with origin AS28001 whose prefix no peer sees AS28001 announce. Many are kept on purpose (backup routes, space announced only in some places).

200.7.86.0/23RADBNo ROA
200.7.86.0/24LACNICValid
200.10.60.0/23LACNIC, RADBValid
2001:13c7:7010::/46LACNICValid
2801:1b8::/44LACNICValid

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.