Network · data from 2026-11-12

AS5656 ACCESSUS-DOM

Registry name: ACCESSUS-DOM - accessU.S./BASENet, US · PeeringDB

5IPv4 routes 0.0% RPKI valid · 80.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

5No ROA 1 with no route object for this origin

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

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

Announced routes

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


207.206.128.0/18	No ROA	None	673 100%	67
207.230.32.0/19	No ROA	Other IRR onlyRADB	673 100%	67
209.74.128.0/18	No ROA	Other IRR onlyRADB	673 100%	67
209.145.128.0/18	No ROA	Other IRR onlyRADB	673 100%	67
216.178.0.0/19	No ROA	Other IRR onlyRADB	673 100%	67

AS-SET

AS5656'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 10 are in fix.csv.

ROA: none5
Route object: none1
Route object: RIR4

Change	Prefix or set	Detail	Full-table peers
ROA: none	207.206.128.0/18	No ROA covers it. Add a ROA for AS5656, maxLength 18.	673 of 673
Route object: none	207.206.128.0/18	No route object for it. Add a route object with origin AS5656 in the RIR database for the space.	673 of 673
ROA: none	207.230.32.0/19	No ROA covers it. Add a ROA for AS5656, maxLength 19.	673 of 673
Route object: RIR	207.230.32.0/19	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	209.74.128.0/18	No ROA covers it. Add a ROA for AS5656, maxLength 18.	673 of 673
Route object: RIR	209.74.128.0/18	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	209.145.128.0/18	No ROA covers it. Add a ROA for AS5656, maxLength 18.	673 of 673
Route object: RIR	209.145.128.0/18	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	216.178.0.0/19	No ROA covers it. Add a ROA for AS5656, maxLength 19.	673 of 673
Route object: RIR	216.178.0.0/19	Route object only in RADB. Add it in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

207.206.128.0/18

No ROA covers it. Add a ROA for AS5656, maxLength 18.

673 of 673

Route object: none

207.206.128.0/18

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

673 of 673

ROA: none

207.230.32.0/19

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

673 of 673

Route object: RIR

207.230.32.0/19

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

673 of 673

ROA: none

209.74.128.0/18

No ROA covers it. Add a ROA for AS5656, maxLength 18.

673 of 673

Route object: RIR

209.74.128.0/18

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

673 of 673

ROA: none

209.145.128.0/18

No ROA covers it. Add a ROA for AS5656, maxLength 18.

673 of 673

Route object: RIR

209.145.128.0/18

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

673 of 673

ROA: none

216.178.0.0/19

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

673 of 673

Route object: RIR

216.178.0.0/19

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

673 of 673

Route objects not announced

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