Network · data from 2026-11-12

AS43359 Tarhely.Eu

Registry name: tarhely Tarhely.Eu Szolgaltato Kft., HU · PeeringDB

8IPv4 routes 75.0% RPKI valid · 100.0% with a route object

2IPv6 routes 0.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

4No ROA 0 with no route object for this origin

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

0Route objects not announced registered with origin AS43359, seen from no peer

Announced routes

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


185.51.188.0/22	No ROA	RIR databaseRIPE	673 100%	66
185.208.224.0/22	No ROA	RIR databaseRIPE	673 100%	66
2a01:b5e0::/32	No ROA	RIR databaseRIPE	636 100%	67
2a0b:3dc0::/32	No ROA	RIR databaseRIPE	636 100%	67
79.172.239.0/24	Valid	RIR databaseRIPE	673 100%	66
79.172.252.0/24	Valid	RIR databaseRIPE	673 100%	66
87.229.68.0/24	Valid	RIR databaseRIPE	673 100%	66
87.229.76.0/24	Valid	RIR databaseRIPE	673 100%	66
178.238.208.0/24	Valid	RIR databaseRIPE	673 100%	66
178.238.222.0/24	Valid	RIR databaseRIPE	673 100%	66

AS-SET

PeeringDB's irr_as_set for AS43359: AS-TARHELYEU. 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 (AS43359 isn't in the set, or no route object for AS43359 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.

Name	Database	ASNs	Sets	Route objects	AS43359 in it	Not covered
AS-TARHELYEU	RIPE	1	1	10	Yes	0

Name

Database

ASNs

Sets

Route objects

AS43359 in it

Not covered

AS-TARHELYEU

RIPE

Yes

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: none4

Change	Prefix or set	Detail	Full-table peers
ROA: none	185.51.188.0/22	No ROA covers it. Add a ROA for AS43359, maxLength 22.	673 of 673
ROA: none	185.208.224.0/22	No ROA covers it. Add a ROA for AS43359, maxLength 22.	673 of 673
ROA: none	2a01:b5e0::/32	No ROA covers it. Add a ROA for AS43359, maxLength 32.	636 of 636
ROA: none	2a0b:3dc0::/32	No ROA covers it. Add a ROA for AS43359, maxLength 32.	636 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

185.51.188.0/22

No ROA covers it. Add a ROA for AS43359, maxLength 22.

673 of 673

ROA: none

185.208.224.0/22

No ROA covers it. Add a ROA for AS43359, maxLength 22.

673 of 673

ROA: none

2a01:b5e0::/32

No ROA covers it. Add a ROA for AS43359, maxLength 32.

636 of 636

ROA: none

2a0b:3dc0::/32

No ROA covers it. Add a ROA for AS43359, maxLength 32.

636 of 636

Route objects not announced

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