bgpreport

Network · data from 2026-11-12

AS203622 gsp GSP LLC

Registry name: gsp GSP LLC, AZ · not in PeeringDB

39IPv4 routes 74.4% RPKI valid · 74.4% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
10No ROA 10 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
14Route objects not announced registered with origin AS203622, seen from no peer

Announced routes

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

95.86.180.0/24 No ROA None 261 39% 57
95.86.181.0/24 No ROA None 261 39% 57
95.86.182.0/24 No ROA None 261 39% 57
95.86.183.0/24 No ROA None 261 39% 57
95.86.184.0/24 No ROA None 261 39% 57
95.86.185.0/24 No ROA None 261 39% 57
95.86.186.0/24 No ROA None 261 39% 57
95.86.187.0/24 No ROA None 261 39% 57
95.86.188.0/24 No ROA None 261 39% 57
95.86.191.0/24 No ROA None 261 39% 57
95.86.172.0/24 Valid RIR databaseRIPE 673 100% 66
95.86.173.0/24 Valid RIR databaseRIPE 673 100% 66
95.86.174.0/24 Valid RIR databaseRIPE 673 100% 66
95.86.175.0/24 Valid RIR databaseRIPE 673 100% 66
46.32.167.0/24 Valid RIR databaseRIPE 672 100% 66
46.32.189.0/24 Valid RIR databaseRIPE 672 100% 66
46.32.190.0/24 Valid RIR databaseRIPE 672 100% 66
95.86.176.0/24 Valid RIR databaseRIPE 672 100% 66
95.86.177.0/24 Valid RIR databaseRIPE 672 100% 66
95.86.178.0/24 Valid RIR databaseRIPE 672 100% 66
95.86.179.0/24 Valid RIR databaseRIPE 672 100% 66
185.26.184.0/24 Valid RIR databaseRIPE 672 100% 66
185.26.185.0/24 Valid RIR databaseRIPE 672 100% 66
185.26.186.0/24 Valid RIR databaseRIPE 672 100% 66
185.26.187.0/24 Valid RIR databaseRIPE 672 100% 66
185.129.0.0/24 Valid RIR databaseRIPE 672 100% 66
185.129.1.0/24 Valid RIR databaseRIPE 672 100% 66
185.129.2.0/24 Valid RIR databaseRIPE 672 100% 66
185.129.3.0/24 Valid RIR databaseRIPE 672 100% 66
37.18.58.0/24 Valid RIR databaseRIPE 671 100% 66
37.32.72.0/24 Valid RIR databaseRIPE 671 100% 66
46.32.160.0/24 Valid RIR databaseRIPE 671 100% 66
46.32.161.0/24 Valid RIR databaseRIPE 671 100% 66
46.32.164.0/24 Valid RIR databaseRIPE 671 100% 66
46.32.165.0/24 Valid RIR databaseRIPE 671 100% 66
46.32.166.0/24 Valid RIR databaseRIPE 671 100% 66
46.32.170.0/24 Valid RIR databaseRIPE 671 100% 66
46.32.171.0/24 Valid RIR databaseRIPE 671 100% 66
46.32.191.0/24 Valid RIR databaseRIPE 671 100% 66
2a0f:7040::/32 Valid RIR databaseRIPE 635 100% 70

AS-SET

AS203622 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 34 are in fix.csv.

  • ROA: none10
  • Route object: none10
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none95.86.180.0/24No ROA covers it. Add a ROA for AS203622, maxLength 24.261 of 673
Route object: none95.86.180.0/24No route object for it. Add a route object with origin AS203622 in the RIR database for the space.261 of 673
ROA: none95.86.181.0/24No ROA covers it. Add a ROA for AS203622, maxLength 24.261 of 673
Route object: none95.86.181.0/24No route object for it. Add a route object with origin AS203622 in the RIR database for the space.261 of 673
ROA: none95.86.182.0/24No ROA covers it. Add a ROA for AS203622, maxLength 24.261 of 673
Route object: none95.86.182.0/24No route object for it. Add a route object with origin AS203622 in the RIR database for the space.261 of 673
ROA: none95.86.183.0/24No ROA covers it. Add a ROA for AS203622, maxLength 24.261 of 673
Route object: none95.86.183.0/24No route object for it. Add a route object with origin AS203622 in the RIR database for the space.261 of 673
ROA: none95.86.184.0/24No ROA covers it. Add a ROA for AS203622, maxLength 24.261 of 673
Route object: none95.86.184.0/24No route object for it. Add a route object with origin AS203622 in the RIR database for the space.261 of 673
ROA: none95.86.185.0/24No ROA covers it. Add a ROA for AS203622, maxLength 24.261 of 673
Route object: none95.86.185.0/24No route object for it. Add a route object with origin AS203622 in the RIR database for the space.261 of 673
ROA: none95.86.186.0/24No ROA covers it. Add a ROA for AS203622, maxLength 24.261 of 673
Route object: none95.86.186.0/24No route object for it. Add a route object with origin AS203622 in the RIR database for the space.261 of 673
ROA: none95.86.187.0/24No ROA covers it. Add a ROA for AS203622, maxLength 24.261 of 673
Route object: none95.86.187.0/24No route object for it. Add a route object with origin AS203622 in the RIR database for the space.261 of 673
ROA: none95.86.188.0/24No ROA covers it. Add a ROA for AS203622, maxLength 24.261 of 673
Route object: none95.86.188.0/24No route object for it. Add a route object with origin AS203622 in the RIR database for the space.261 of 673
ROA: none95.86.191.0/24No ROA covers it. Add a ROA for AS203622, maxLength 24.261 of 673
Route object: none95.86.191.0/24No route object for it. Add a route object with origin AS203622 in the RIR database for the space.261 of 673

Route objects not announced

Route objects with origin AS203622 whose prefix no peer sees AS203622 announce. Many are kept on purpose (backup routes, space announced only in some places).

46.32.174.0/24RIPEInvalid: origin
185.26.184.0/22RIPENo ROA
185.129.0.0/22RIPENo ROA
2a03:8c0::/32RIPEInvalid: origin
2a03:8c0::/36RIPEInvalid: origin
2a03:8c0:1000::/36RIPEInvalid: origin
2a03:8c0:2000::/36RIPEInvalid: origin
2a03:8c0:3000::/36RIPEInvalid: origin
2a03:8c0:4000::/36RIPEInvalid: origin
2a03:8c0:5000::/36RIPEInvalid: origin
2a03:8c0:6000::/36RIPEInvalid: origin
2a03:8c0:7000::/36RIPEInvalid: origin
2a03:8c0:8000::/36RIPEInvalid: origin
2a03:8c0:9000::/36RIPEInvalid: origin

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.