bgpreport

Network · data from 2026-11-12

AS56345 TELEDISTRIBUCION_BAENA_AS TVB TELEDISTRIBUCION S.L.

Registry name: TELEDISTRIBUCION_BAENA_AS TVB TELEDISTRIBUCION S.L., ES · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS56345, 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.
46.253.232.0/21 No ROA None 673 100% 67
46.253.226.0/23 No ROA Nonecovered by 46.253.224.0/22 672 100% 67
46.253.234.0/23 No ROA Nonecovered by 46.253.232.0/22 672 100% 67
46.253.224.0/21 No ROA RIR databaseRIPE 673 100% 67
46.253.224.0/22 No ROA RIR databaseRIPE 673 100% 67
46.253.228.0/22 No ROA RIR databaseRIPE 673 100% 67
46.253.232.0/22 No ROA RIR databaseRIPE 673 100% 67
46.253.236.0/22 No ROA RIR databaseRIPE 673 100% 67

AS-SET

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

  • ROA: none8
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: none46.253.232.0/21No ROA covers it. Add a ROA for AS56345, maxLength 21.673 of 673
Route object: none46.253.232.0/21No route object for it. Add a route object with origin AS56345 in the RIR database for the space.673 of 673
ROA: none46.253.226.0/23No ROA covers it. Add a ROA for AS56345, maxLength 23.672 of 673
Route object: none46.253.226.0/23No route object for it. A route object for 46.253.224.0/22 with origin AS56345 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56345 in the RIR database for the space.672 of 673
ROA: none46.253.234.0/23No ROA covers it. Add a ROA for AS56345, maxLength 23.672 of 673
Route object: none46.253.234.0/23No route object for it. A route object for 46.253.232.0/22 with origin AS56345 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56345 in the RIR database for the space.672 of 673
ROA: none46.253.224.0/21No ROA covers it. Add a ROA for AS56345, maxLength 21.673 of 673
ROA: none46.253.224.0/22No ROA covers it. Add a ROA for AS56345, maxLength 22.673 of 673
ROA: none46.253.228.0/22No ROA covers it. Add a ROA for AS56345, maxLength 22.673 of 673
ROA: none46.253.232.0/22No ROA covers it. Add a ROA for AS56345, maxLength 22.673 of 673
ROA: none46.253.236.0/22No ROA covers it. Add a ROA for AS56345, maxLength 22.673 of 673

Route objects not announced

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