bgpreport

Network · data from 2026-11-12

AS273043 TV CABLE COM CA

Registry name: AS273043 - TV CABLE COM CA, VE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273043, 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:eb90:2000::/36 Valid Nonecovered by 2803:eb90::/32 635 100% 67
45.192.130.0/24 Valid Other IRR onlyRADB 668 99% 67
45.192.131.0/24 Valid Other IRR onlyRADB 668 99% 67
177.29.224.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
2803:eb90::/32 Valid RIR databaseLACNIC, RADB 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS273043: AS273043:AS-CUSTOMERS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS273043 isn't in the set, or no route object for AS273043 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS273043 in itNot covered
AS273043:AS-CUSTOMERS In no IRR database read today.

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: none1
  • Route object: RIR2
  • AS-SET: not found1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none2803:eb90:2000::/36No route object for it. A route object for 2803:eb90::/32 with origin AS273043 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273043 in the RIR database for the space.635 of 636
Route object: RIR45.192.130.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR45.192.131.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
AS-SET: not foundAS273043:AS-CUSTOMERSPeeringDB names AS273043:AS-CUSTOMERS; no IRR database read has it.

Route objects not announced

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

45.192.130.0/23AFRINICNo ROA
2803:eb90:1100::/40RADBValid

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.