bgpreport

Network · data from 2026-11-12

AS273142 AS273142 - SERVICIOS DE TELCOMUNICACIONES LATEVECOM CIA LTDA

Registry name: AS273142 - SERVICIOS DE TELCOMUNICACIONES LATEVECOM CIA LTDA, EC · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273142, 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.
201.77.57.0/24 Invalid: origin None 2 0%low visibility 2
45.10.107.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
2803:2c50:6000::/36 Valid RIR databaseLACNIC 635 100% 67
2803:2c50::/32 Valid RIR databaseLACNIC, RADB 633 100% 67

AS-SET

AS273142 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 6 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin201.77.57.0/24ROAs covering it name AS39639, not AS273142. If AS273142 should announce it, add a ROA for AS273142.2 of 673
Route object: none201.77.57.0/24No route object for it. Add a route object with origin AS273142 in the RIR database for the space.2 of 673

Route objects not announced

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

2803:2c50:1000::/36LACNICValid
2803:2c50:2000::/36LACNICValid
2803:2c50:3000::/36LACNICValid
2803:2c50:a000::/36LACNICValid

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.