Network · data from 2026-11-12

AS27288 Digital Path

Registry name: DPCHICO-1 - Digital Path, US · PeeringDB

10IPv4 routes 60.0% RPKI valid · 80.0% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

4No ROA 2 with no route object for this origin

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

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

Announced routes

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


65.164.104.0/24	No ROA	None	673 100%	67
38.80.224.0/21	No ROA	Nonecovered by 38.80.224.0/19	671 100%	67
12.172.178.0/23	No ROA	Other IRR onlyRADB	671 100%	67
38.80.224.0/19	No ROA	Other IRR onlyRADB	671 100%	67
198.204.208.0/20	Valid	RIR databaseARIN	673 100%	67
208.53.64.0/19	Valid	RIR databaseARIN	673 100%	67
208.53.64.0/20	Valid	RIR databaseARIN	673 100%	67
162.246.132.0/22	Valid	RIR databaseARIN	671 100%	67
162.247.32.0/22	Valid	RIR databaseARIN	671 100%	67
198.204.216.0/21	Valid	RIR databaseARIN	671 100%	67
2605:5d00::/32	Valid	RIR databaseARIN, RADB	605 95%	67

AS-SET

AS27288'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 8 are in fix.csv.

ROA: none4
Route object: none2
Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
ROA: none	65.164.104.0/24	No ROA covers it. Add a ROA for AS27288, maxLength 24.	673 of 673
Route object: none	65.164.104.0/24	No route object for it. Add a route object with origin AS27288 in the RIR database for the space.	673 of 673
ROA: none	38.80.224.0/21	No ROA covers it. Add a ROA for AS27288, maxLength 21.	671 of 673
Route object: none	38.80.224.0/21	No route object for it. A route object for 38.80.224.0/19 with origin AS27288 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27288 in the RIR database for the space.	671 of 673
ROA: none	12.172.178.0/23	No ROA covers it. Add a ROA for AS27288, maxLength 23.	671 of 673
Route object: RIR	12.172.178.0/23	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
ROA: none	38.80.224.0/19	No ROA covers it. Add a ROA for AS27288, maxLength 19.	671 of 673
Route object: RIR	38.80.224.0/19	Route object only in RADB. Add it in the RIR database for the space.	671 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

65.164.104.0/24

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

673 of 673

Route object: none

65.164.104.0/24

No route object for it. Add a route object with origin AS27288 in the RIR database for the space.

673 of 673

ROA: none

38.80.224.0/21

No ROA covers it. Add a ROA for AS27288, maxLength 21.

671 of 673

Route object: none

38.80.224.0/21

No route object for it. A route object for 38.80.224.0/19 with origin AS27288 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27288 in the RIR database for the space.

671 of 673

ROA: none

12.172.178.0/23

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

671 of 673

Route object: RIR

12.172.178.0/23

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

671 of 673

ROA: none

38.80.224.0/19

No ROA covers it. Add a ROA for AS27288, maxLength 19.

671 of 673

Route object: RIR

38.80.224.0/19

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

671 of 673

Route objects not announced

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