bgpreport

Network · data from 2026-11-12

AS46090 AMX - LATAM Telecommunications, L.L.C.

Registry name: AMX - LATAM Telecommunications, L.L.C., US · not in PeeringDB

6IPv4 routes 66.7% RPKI valid · 66.7% with a route object
4IPv6 routes 0.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No ROA 6 with no route object for this origin
6Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS46090, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS46090, 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.
190.116.130.208/31 No ROA None 2 0%low visibility 2
190.116.130.214/31 No ROA None 2 0%low visibility 2
2800:200::c:62/127 No ROA None 1 0%low visibility 1
2800:200::c:462a/127 No ROA None 1 0%low visibility 1
2800:200::c:462c/127 No ROA None 1 0%low visibility 1
2800:200::c:462e/127 No ROA None 1 0%low visibility 1
187.174.68.0/24 Valid RIR databaseLACNIC 673 100% 67
187.174.66.0/24 Valid RIR databaseLACNIC 672 100% 67
187.174.67.0/24 Valid RIR databaseLACNIC 672 100% 67
187.214.28.0/24 Valid RIR databaseLACNIC 672 100% 67

AS-SET

AS46090 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 12 are in fix.csv.

  • ROA: none6
  • Route object: none6
ChangePrefix or setDetailFull-table peers
ROA: none190.116.130.208/31No ROA covers it. Add a ROA for AS46090, maxLength 31.2 of 673
Route object: none190.116.130.208/31No route object for it. Add a route object with origin AS46090 in the RIR database for the space.2 of 673
ROA: none190.116.130.214/31No ROA covers it. Add a ROA for AS46090, maxLength 31.2 of 673
Route object: none190.116.130.214/31No route object for it. Add a route object with origin AS46090 in the RIR database for the space.2 of 673
ROA: none2800:200::c:62/127No ROA covers it. Add a ROA for AS46090, maxLength 127.1 of 636
Route object: none2800:200::c:62/127No route object for it. Add a route object with origin AS46090 in the RIR database for the space.1 of 636
ROA: none2800:200::c:462a/127No ROA covers it. Add a ROA for AS46090, maxLength 127.1 of 636
Route object: none2800:200::c:462a/127No route object for it. Add a route object with origin AS46090 in the RIR database for the space.1 of 636
ROA: none2800:200::c:462c/127No ROA covers it. Add a ROA for AS46090, maxLength 127.1 of 636
Route object: none2800:200::c:462c/127No route object for it. Add a route object with origin AS46090 in the RIR database for the space.1 of 636
ROA: none2800:200::c:462e/127No ROA covers it. Add a ROA for AS46090, maxLength 127.1 of 636
Route object: none2800:200::c:462e/127No route object for it. Add a route object with origin AS46090 in the RIR database for the space.1 of 636

Route objects not announced

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