bgpreport

Network · data from 2026-11-12

AS43529 Vidanet Cabletelevision Provider

Registry name: VIDANET-AS ViDaNet Cabletelevision Provider Ltd., HU · PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 routes 66.7% RPKI valid · 66.7% 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
2Route objects not announced registered with origin AS43529, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS43529, 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.
2001:4c4c:3000::/36 Invalid: origin None 9 1%low visibility 11
46.251.16.0/20 Valid RIR databaseRIPE 673 100% 67
79.121.0.0/18 Valid RIR databaseRIPE 673 100% 67
79.121.64.0/21 Valid RIR databaseRIPE 673 100% 67
79.121.88.0/21 Valid RIR databaseRIPE 673 100% 67
94.248.128.0/19 Valid RIR databaseRIPE 673 100% 67
94.248.192.0/19 Valid RIR databaseRIPE 673 100% 67
94.248.240.0/21 Valid RIR databaseRIPE 673 100% 67
2a03:bf00:200::/40 Valid RIR databaseRIPE 628 99% 67
2a03:bf01::/32 Valid RIR databaseRIPE 628 99% 67

AS-SET

AS43529's PeeringDB record names no 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 4 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin2001:4c4c:3000::/36ROAs covering it name AS5483, not AS43529. If AS43529 should announce it, add a ROA for AS43529.9 of 636
Route object: none2001:4c4c:3000::/36No route object for it. Add a route object with origin AS43529 in the RIR database for the space.9 of 636

Route objects not announced

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

91.147.192.0/21RIPENo ROA
94.248.240.0/20RIPENo ROA

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.