bgpreport

Network · data from 2026-11-12

AS274160 AS274160 - TV STAR SATELLITE C.A

Registry name: AS274160 - TV STAR SATELLITE C.A, VE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274160, 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.

2803:39d0:20::/48 Valid Nonecovered by 2803:39d0::/32 635 100% 67
2803:39d0:69::/48 Valid Nonecovered by 2803:39d0::/32 635 100% 68
2803:39d0:1000::/48 Valid Nonecovered by 2803:39d0::/32 630 99% 67
2803:39d0:4000::/48 Valid Nonecovered by 2803:39d0::/32 630 99% 67
2803:39d0:63::/48 Valid Other IRR onlyRADB 635 100% 68
2803:39d0:fffe::/48 Valid Other IRR onlyRADB 635 100% 68
38.103.210.0/24 Valid RIR databaseARIN, RADB 671 100% 67
38.19.227.0/24 Valid RIR databaseARIN, RADB 669 99% 67
38.113.87.0/24 Valid RIR databaseARIN, RADB 668 99% 67
154.58.234.0/24 Valid RIR databaseARIN, RADB 668 99% 66
2803:39d0::/32 Valid RIR databaseLACNIC, RADB 632 99% 69

AS-SET

AS274160 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.

  • Route object: none4
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none2803:39d0:20::/48No route object for it. A route object for 2803:39d0::/32 with origin AS274160 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274160 in the RIR database for the space.635 of 636
Route object: none2803:39d0:69::/48No route object for it. A route object for 2803:39d0::/32 with origin AS274160 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274160 in the RIR database for the space.635 of 636
Route object: none2803:39d0:1000::/48No route object for it. A route object for 2803:39d0::/32 with origin AS274160 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274160 in the RIR database for the space.630 of 636
Route object: none2803:39d0:4000::/48No route object for it. A route object for 2803:39d0::/32 with origin AS274160 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274160 in the RIR database for the space.630 of 636
Route object: RIR2803:39d0:63::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2803:39d0:fffe::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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