Network · data from 2026-11-12

AS62605 Untangled Technology

Registry name: UNTANGLEDTECH - Untangled Technology, LLC, US · PeeringDB

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

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

2No 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 AS62605, seen from no peer

Announced routes

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


66.219.167.0/24	No ROA	RIR databaseARIN	671 100%	68
66.219.169.0/24	No ROA	RIR databaseARIN	671 100%	68
192.64.176.0/20	Valid	RIR databaseARIN	671 100%	68
2607:c940::/32	Valid	RIR databaseARIN	635 100%	69

AS-SET

AS62605'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 2 are in fix.csv.

ROA: none2

Change	Prefix or set	Detail	Full-table peers
ROA: none	66.219.167.0/24	No ROA covers it. Add a ROA for AS62605, maxLength 24.	671 of 673
ROA: none	66.219.169.0/24	No ROA covers it. Add a ROA for AS62605, maxLength 24.	671 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

66.219.167.0/24

No ROA covers it. Add a ROA for AS62605, maxLength 24.

671 of 673

ROA: none

66.219.169.0/24

No ROA covers it. Add a ROA for AS62605, maxLength 24.

671 of 673

Route objects not announced

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