Network · data from 2026-11-12

AS47159 CELLKABEL Celldomolki Kabeltelevizio Kft.

Registry name: CELLKABEL Celldomolki Kabeltelevizio Kft., HU · not in PeeringDB

34IPv4 routes 97.1% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

1No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

2Route objects not announced registered with origin AS47159, seen from no peer

Announced routes

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


45.88.94.0/23	No ROA	RIR databaseRIPE	673 100%	66
62.77.213.0/24	Valid	RIR databaseRIPE	673 100%	66
62.77.234.0/24	Valid	RIR databaseRIPE	673 100%	66
79.121.124.0/22	Valid	RIR databaseRIPE	673 100%	66
79.172.229.0/24	Valid	RIR databaseRIPE	673 100%	66
79.172.244.0/22	Valid	RIR databaseRIPE	673 100%	66
82.131.172.0/24	Valid	RIR databaseRIPE	673 100%	66
87.229.20.0/23	Valid	RIR databaseRIPE	673 100%	66
87.229.60.0/22	Valid	RIR databaseRIPE	673 100%	66
87.229.86.0/23	Valid	RIR databaseRIPE	673 100%	66
87.229.88.0/22	Valid	RIR databaseRIPE	673 100%	66
87.229.117.0/24	Valid	RIR databaseRIPE	673 100%	66
87.229.122.0/23	Valid	RIR databaseRIPE	673 100%	66
88.87.232.0/21	Valid	RIR databaseRIPE	673 100%	66
88.132.208.0/22	Valid	RIR databaseRIPE	673 100%	66
88.132.212.0/22	Valid	RIR databaseRIPE	673 100%	66
88.132.216.0/21	Valid	RIR databaseRIPE	673 100%	66
88.132.244.0/22	Valid	RIR databaseRIPE	673 100%	66
88.132.248.0/22	Valid	RIR databaseRIPE	673 100%	66
89.186.104.0/24	Valid	RIR databaseRIPE	673 100%	66
91.83.92.0/24	Valid	RIR databaseRIPE	673 100%	66
91.83.158.0/24	Valid	RIR databaseRIPE	673 100%	66
91.83.220.0/22	Valid	RIR databaseRIPE	673 100%	66
91.83.225.0/24	Valid	RIR databaseRIPE	673 100%	66
91.147.216.0/21	Valid	RIR databaseRIPE	673 100%	66
94.248.176.0/21	Valid	RIR databaseRIPE	673 100%	66
95.138.197.0/24	Valid	RIR databaseRIPE	673 100%	66
95.138.198.0/24	Valid	RIR databaseRIPE	673 100%	66
95.138.199.0/24	Valid	RIR databaseRIPE	673 100%	66
213.181.192.0/22	Valid	RIR databaseRIPE	673 100%	66
213.181.208.0/23	Valid	RIR databaseRIPE	673 100%	66
213.181.213.0/24	Valid	RIR databaseRIPE	673 100%	66
213.181.214.0/23	Valid	RIR databaseRIPE	673 100%	66
213.197.64.0/22	Valid	RIR databaseRIPE	673 100%	66

AS-SET

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

ROA: none1
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
ROA: none	45.88.94.0/23	No ROA covers it. Add a ROA for AS47159, maxLength 23.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

45.88.94.0/23

No ROA covers it. Add a ROA for AS47159, maxLength 23.

673 of 673

Route objects not announced

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


109.110.152.0/21	RIPE	Invalid: origin
2a01:9b80::/32	RIPE	Valid

109.110.152.0/21

RIPE

Invalid: origin

2a01:9b80::/32

RIPE

Valid

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.