Network · data from 2026-11-12

AS400639 Outer Reach Broadband LLC

Registry name: ORB-ASN-ME-1 - Outer Reach Broadband LLC, US · PeeringDB

3IPv4 routes 66.7% 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

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

Announced routes

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


38.252.180.0/22	No ROA	Other IRR onlyRADB	669 99%	68
23.160.124.0/24	Valid	RIR databaseARIN	669 99%	68
205.164.108.0/22	Valid	RIR databaseARIN, RADB	669 99%	68

AS-SET

AS400639'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: none1
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
ROA: none	38.252.180.0/22	No ROA covers it. Add a ROA for AS400639, maxLength 22.	669 of 673
Route object: RIR	38.252.180.0/22	Route object only in RADB. Add it in the RIR database for the space.	669 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

38.252.180.0/22

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

669 of 673

Route object: RIR

38.252.180.0/22

Route object only in RADB. Add it in the RIR database for the space.

669 of 673

Route objects not announced

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