Network · data from 2026-11-12

AS19616 ACCESS-OHIO - ACCESS

Registry name: ACCESS-OHIO - ACCESS, US · not in PeeringDB

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

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

3No ROA 2 with no route object for this origin

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

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

Announced routes

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


64.18.32.0/21	No ROA	Nonecovered by 64.18.32.0/20	20 3%low visibility	18
64.18.40.0/21	No ROA	Nonecovered by 64.18.32.0/20	20 3%low visibility	18
64.18.32.0/20	No ROA	Other IRR onlyRADB	670 100%	69

64.18.32.0/21

No ROA

Nonecovered by 64.18.32.0/20

20 3%low visibility

64.18.40.0/21

No ROA

Nonecovered by 64.18.32.0/20

20 3%low visibility

64.18.32.0/20

No ROA

Other IRR onlyRADB

670 100%

AS-SET

AS19616 isn't in PeeringDB, where networks name their 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 6 are in fix.csv.

ROA: none3
Route object: none2
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
ROA: none	64.18.32.0/21	No ROA covers it. Add a ROA for AS19616, maxLength 21.	20 of 673
Route object: none	64.18.32.0/21	No route object for it. A route object for 64.18.32.0/20 with origin AS19616 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19616 in the RIR database for the space.	20 of 673
ROA: none	64.18.40.0/21	No ROA covers it. Add a ROA for AS19616, maxLength 21.	20 of 673
Route object: none	64.18.40.0/21	No route object for it. A route object for 64.18.32.0/20 with origin AS19616 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19616 in the RIR database for the space.	20 of 673
ROA: none	64.18.32.0/20	No ROA covers it. Add a ROA for AS19616, maxLength 20.	670 of 673
Route object: RIR	64.18.32.0/20	Route object only in RADB. Add it in the RIR database for the space.	670 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

64.18.32.0/21

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

20 of 673

Route object: none

64.18.32.0/21

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

20 of 673

ROA: none

64.18.40.0/21

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

20 of 673

Route object: none

64.18.40.0/21

20 of 673

ROA: none

64.18.32.0/20

No ROA covers it. Add a ROA for AS19616, maxLength 20.

670 of 673

Route object: RIR

64.18.32.0/20

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

670 of 673

Route objects not announced

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