Network · data from 2026-11-12

AS41206 United Telecom Zrt.

Registry name: United-Telecom-HU-AS United Telecom Zartkoruen Mukodo Reszvenytarsasag, HU · PeeringDB

3IPv4 routes 0.0% RPKI valid · 100.0% with a route object

1IPv6 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 AS41206, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS41206, 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.219.48.0/22	No ROA	RIR databaseRIPE	672 100%	67
185.219.50.0/23	No ROA	RIR databaseRIPE	672 100%	67
185.219.48.0/23	No ROA	RIR databaseRIPE	670 100%	67
2a0b:e0c0::/29	No ROA	RIR databaseRIPE	635 100%	67

AS-SET

PeeringDB's irr_as_set for AS41206: RIPE::AS-UNITEDTELECOM. 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 (AS41206 isn't in the set, or no route object for AS41206 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	AS41206 in it	Not covered
RIPE::AS-UNITEDTELECOM	RIPElists itself further down1 member set in no database: AS-HPWR	61	14	2,522	Yes	0

Name

Database

ASNs

Sets

Route objects

AS41206 in it

Not covered

RIPE::AS-UNITEDTELECOM

RIPElists itself further down1 member set in no database: AS-HPWR

2,522

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

ROA: none4
AS-SET: missing member1

Change	Prefix or set	Detail	Full-table peers
ROA: none	185.219.48.0/22	No ROA covers it. Add a ROA for AS41206, maxLength 22.	672 of 673
ROA: none	185.219.50.0/23	No ROA covers it. Add a ROA for AS41206, maxLength 23.	672 of 673
ROA: none	185.219.48.0/23	No ROA covers it. Add a ROA for AS41206, maxLength 23.	670 of 673
ROA: none	2a0b:e0c0::/29	No ROA covers it. Add a ROA for AS41206, maxLength 29.	635 of 636
AS-SET: missing member	RIPE::AS-UNITEDTELECOM	AS-UNITEDTELECOM (RIPE) lists AS-HPWR; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

ROA: none

185.219.48.0/22

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

672 of 673

ROA: none

185.219.50.0/23

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

672 of 673

ROA: none

185.219.48.0/23

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

670 of 673

ROA: none

2a0b:e0c0::/29

No ROA covers it. Add a ROA for AS41206, maxLength 29.

635 of 636

AS-SET: missing member

RIPE::AS-UNITEDTELECOM

AS-UNITEDTELECOM (RIPE) lists AS-HPWR; no IRR database read has it.

Route objects not announced

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