Network · data from 2026-11-12

AS8175 High Speed Web, Inc.

Registry name: HIGHSPEEDWEB - High Speed Web/Genesis 2 Networks, US · PeeringDB

6IPv4 routes 50.0% RPKI valid · 50.0% with a route object

0IPv6 routes

2RPKI invalid 1 origin · 1 maxLength

1No ROA 3 with no route object for this origin

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

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

Announced routes

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


69.85.80.0/20	Invalid: origin	Other origin only	3 0%low visibility	3
216.189.10.0/24	Invalid: maxLength	Nonecovered by 216.189.0.0/17	4 1%low visibility	3
206.253.160.0/21	No ROA	Other origin only	669 99%	69
69.51.0.0/19	Valid	RIR databaseARIN	669 99%	67
209.198.0.0/18	Valid	RIR databaseARIN	669 99%	67
216.189.0.0/17	Valid	RIR databaseARIN	669 99%	67

69.85.80.0/20

Invalid: origin

Other origin only

3 0%low visibility

216.189.10.0/24

Invalid: maxLength

Nonecovered by 216.189.0.0/17

4 1%low visibility

206.253.160.0/21

No ROA

Other origin only

669 99%

69.51.0.0/19

Valid

RIR databaseARIN

669 99%

209.198.0.0/18

Valid

RIR databaseARIN

669 99%

216.189.0.0/17

Valid

RIR databaseARIN

669 99%

AS-SET

AS8175'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 6 are in fix.csv.

ROA: origin1
ROA: maxLength1
ROA: none1
Route object: none3

Change	Prefix or set	Detail	Full-table peers
ROA: origin	69.85.80.0/20	ROAs covering it name AS27569, not AS8175. If AS8175 should announce it, add a ROA for AS8175.	3 of 673
Route object: none	69.85.80.0/20	Route objects for it name AS27569. Add a route object with origin AS8175 in the RIR database for the space.	3 of 673
ROA: maxLength	216.189.10.0/24	ROA 216.189.0.0/17 AS8175 has maxLength 17; the route is a /24. Raise the maxLength, or add a ROA for 216.189.10.0/24.	4 of 673
Route object: none	216.189.10.0/24	No route object for it. A route object for 216.189.0.0/17 with origin AS8175 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8175 in the RIR database for the space.	4 of 673
ROA: none	206.253.160.0/21	No ROA covers it. Add a ROA for AS8175, maxLength 21.	669 of 673
Route object: none	206.253.160.0/21	Route objects for it name AS1299, AS6921, AS12100. Add a route object with origin AS8175 in the RIR database for the space.	669 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

69.85.80.0/20

ROAs covering it name AS27569, not AS8175. If AS8175 should announce it, add a ROA for AS8175.

3 of 673

Route object: none

69.85.80.0/20

Route objects for it name AS27569. Add a route object with origin AS8175 in the RIR database for the space.

3 of 673

ROA: maxLength

216.189.10.0/24

ROA 216.189.0.0/17 AS8175 has maxLength 17; the route is a /24. Raise the maxLength, or add a ROA for 216.189.10.0/24.

4 of 673

Route object: none

216.189.10.0/24

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

4 of 673

ROA: none

206.253.160.0/21

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

669 of 673

Route object: none

206.253.160.0/21

Route objects for it name AS1299, AS6921, AS12100. Add a route object with origin AS8175 in the RIR database for the space.

669 of 673

Route objects not announced

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