bgpreport

Network · data from 2026-11-12

AS264845 AS264845 - LACNIC - Latin American and Caribbean IP address

Registry name: AS264845 - LACNIC - Latin American and Caribbean IP address, UY · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264845, 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.
2800:700::/48 Invalid: origin None 59 9%low visibility 32
190.112.53.0/24 Valid Nonecovered by 190.112.52.0/22 671 100% 66
190.112.54.0/24 Valid Nonecovered by 190.112.52.0/22 671 100% 66
190.112.52.0/24 Valid Nonecovered by 190.112.52.0/22 670 100% 66
201.219.252.0/23 Valid RIR databaseLACNIC 673 100% 66
190.112.52.0/22 Valid RIR databaseLACNIC, RADB 672 100% 66
2001:13c7:7020::/48 Valid RIR databaseLACNIC, RADB 634 100% 68

AS-SET

AS264845 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 5 are in fix.csv.

  • ROA: origin1
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: origin2800:700::/48ROAs covering it name AS1111, AS1212, AS1313, AS52266, AS232323, not AS264845. If AS264845 should announce it, add a ROA for AS264845.59 of 636
Route object: none2800:700::/48No route object for it. Add a route object with origin AS264845 in the RIR database for the space.59 of 636
Route object: none190.112.53.0/24No route object for it. A route object for 190.112.52.0/22 with origin AS264845 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264845 in the RIR database for the space.671 of 673
Route object: none190.112.54.0/24No route object for it. A route object for 190.112.52.0/22 with origin AS264845 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264845 in the RIR database for the space.671 of 673
Route object: none190.112.52.0/24No route object for it. A route object for 190.112.52.0/22 with origin AS264845 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264845 in the RIR database for the space.670 of 673

Route objects not announced

Every route object with origin AS264845 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.