bgpreport

Network · data from 2026-11-12

AS273934 AS273934 - A & D FOR CABLE TELEVISION IN THE SOUTHERN PERU SAC

Registry name: AS273934 - A & D FOR CABLE TELEVISION IN THE SOUTHERN PERU SAC, PE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273934, 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.
38.137.200.0/23 No ROA Other IRR onlyRADB 671 100% 67
138.204.168.0/24 Valid Nonecovered by 138.204.168.0/22 672 100% 67
138.204.169.0/24 Valid Nonecovered by 138.204.168.0/22 672 100% 67
138.204.170.0/24 Valid Nonecovered by 138.204.168.0/22 672 100% 67
138.204.171.0/24 Valid Nonecovered by 138.204.168.0/22 672 100% 67
138.204.168.0/22 Valid RIR databaseLACNIC 672 100% 67
38.137.200.0/24 Valid RIR databaseARIN 24 4%low visibility 11
38.137.201.0/24 Valid RIR databaseARIN 24 4%low visibility 11

AS-SET

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

  • ROA: none1
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none38.137.200.0/23No ROA covers it. Add a ROA for AS273934, maxLength 23.671 of 673
Route object: RIR38.137.200.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: none138.204.168.0/24No route object for it. A route object for 138.204.168.0/22 with origin AS273934 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273934 in the RIR database for the space.672 of 673
Route object: none138.204.169.0/24No route object for it. A route object for 138.204.168.0/22 with origin AS273934 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273934 in the RIR database for the space.672 of 673
Route object: none138.204.170.0/24No route object for it. A route object for 138.204.168.0/22 with origin AS273934 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273934 in the RIR database for the space.672 of 673
Route object: none138.204.171.0/24No route object for it. A route object for 138.204.168.0/22 with origin AS273934 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273934 in the RIR database for the space.672 of 673

Route objects not announced

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

2803:b0e0:8002::/48LACNIC, RADBValid

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.