bgpreport

Network · data from 2026-11-12

AS22769 Valley Strong Credit Union

Registry name: VSCU-1 - Valley Strong Credit Union, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22769, 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.
198.101.26.0/24 No ROA None 673 100% 67

AS-SET

AS22769'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 108 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced106
ChangePrefix or setDetailFull-table peers
ROA: none198.101.26.0/24No ROA covers it. Add a ROA for AS22769, maxLength 24.673 of 673
Route object: none198.101.26.0/24No route object for it. Add a route object with origin AS22769 in the RIR database for the space.673 of 673

Route objects not announced

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

41.77.240.0/21NTTCOMNo ROA
43.229.120.0/22NTTCOM, RADBNo ROA
43.246.212.0/22NTTCOM, RADBNo ROA
43.246.213.0/24NTTCOMNo ROA
43.246.214.0/23NTTCOMNo ROA
45.93.16.0/22NTTCOMNo ROA
45.114.12.0/22NTTCOMNo ROA
45.114.12.0/24NTTCOMNo ROA
45.114.13.0/24NTTCOM, RADBNo ROA
45.114.14.0/24NTTCOM, RADBNo ROA
45.114.15.0/24NTTCOM, RADBNo ROA
45.125.28.0/22NTTCOM, RADBNo ROA
45.125.104.0/22NTTCOM, RADBNo ROA
45.134.144.0/22NTTCOMNo ROA
62.60.200.0/21NTTCOMNo ROA
89.33.128.0/23NTTCOMNo ROA
91.209.182.0/24NTTCOMNo ROA
91.244.196.0/22NTTCOMNo ROA
92.118.204.0/22NTTCOMNo ROA
98.159.38.0/23NTTCOMNo ROA
103.35.200.0/22NTTCOM, RADBNo ROA
103.48.144.0/22RADBNo ROA
103.53.216.0/22NTTCOM, RADBNo ROA
103.53.216.0/23NTTCOM, RADBNo ROA
103.53.216.0/24NTTCOM, RADBNo ROA
103.53.217.0/24NTTCOM, RADBNo ROA
103.53.218.0/23NTTCOM, RADBNo ROA
103.53.218.0/24NTTCOM, RADBNo ROA
103.53.219.0/24NTTCOM, RADBNo ROA
103.95.116.0/22NTTCOM, RADBNo ROA
103.103.220.0/22NTTCOMNo ROA
103.103.224.0/21NTTCOM, RADBNo ROA
103.103.224.0/22NTTCOMNo ROA
103.103.228.0/22NTTCOM, RADBNo ROA
103.103.232.0/22NTTCOM, RADBNo ROA
103.103.248.0/21NTTCOM, RADBNo ROA
103.103.248.0/22NTTCOM, RADBNo ROA
103.103.252.0/22NTTCOM, RADBNo ROA
103.104.0.0/21NTTCOM, RADBNo ROA
103.104.0.0/22NTTCOM, RADBNo ROA
103.104.4.0/22NTTCOMNo ROA
103.144.148.0/23NTTCOMNo ROA
103.193.144.0/22NTTCOM, RADBNo ROA
103.193.240.0/22NTTCOM, RADBNo ROA
103.203.148.0/22NTTCOM, RADBNo ROA
103.212.104.0/22NTTCOM, RADBNo ROA
103.215.8.0/22NTTCOM, RADBNo ROA
103.215.76.0/22NTTCOM, RADBNo ROA
103.231.187.0/24NTTCOM, RADBNo ROA
139.5.208.0/22NTTCOM, RADBNo ROA
144.48.196.0/22NTTCOM, RADBNo ROA
146.196.80.0/23NTTCOMNo ROA
146.196.80.0/24APNIC, NTTCOMNo ROA
146.196.81.0/24APNIC, NTTCOMNo ROA
154.92.192.0/22NTTCOM, RADBNo ROA
154.92.192.0/23NTTCOM, RADBNo ROA
154.92.194.0/23NTTCOM, RADBNo ROA
154.213.160.0/19NTTCOMNo ROA
154.213.160.0/20NTTCOM, RADBNo ROA
160.119.79.0/24NTTCOMNo ROA
175.176.180.0/22NTTCOM, RADBNo ROA
176.105.228.0/22NTTCOMNo ROA
185.143.72.0/24NTTCOMNo ROA
185.177.24.0/22NTTCOMNo ROA
185.235.164.0/22NTTCOMNo ROA
185.245.0.0/22NTTCOM, RADBNo ROA
193.107.216.0/22NTTCOM, RADBNo ROA
194.62.214.0/23NTTCOMNo ROA
194.76.0.0/23NTTCOMNo ROA
197.231.208.0/22NTTCOMNo ROA
202.5.28.0/24NTTCOMNo ROA
202.5.30.0/24NTTCOMNo ROA
212.95.128.0/19NTTCOMNo ROA
212.95.128.0/20NTTCOM, RADBNo ROA
212.95.128.0/21NTTCOM, RADBNo ROA
212.95.128.0/22NTTCOM, RADBNo ROA
212.95.128.0/23NTTCOM, RADBNo ROA
212.95.130.0/23NTTCOM, RADBNo ROA
212.95.132.0/22NTTCOM, RADBNo ROA
212.95.132.0/23NTTCOM, RADBNo ROA
212.95.134.0/23NTTCOM, RADBNo ROA
212.95.136.0/21NTTCOM, RADBNo ROA
212.95.136.0/22NTTCOM, RADBNo ROA
212.95.136.0/23NTTCOM, RADBNo ROA
212.95.138.0/23NTTCOM, RADBNo ROA
212.95.140.0/22NTTCOM, RADBNo ROA
212.95.140.0/23NTTCOM, RADBNo ROA
212.95.142.0/23NTTCOM, RADBNo ROA
212.95.144.0/20NTTCOM, RADBNo ROA
212.95.144.0/21NTTCOM, RADBNo ROA
212.95.144.0/22NTTCOM, RADBNo ROA
212.95.144.0/23NTTCOM, RADBNo ROA
212.95.146.0/23NTTCOM, RADBNo ROA
212.95.148.0/22NTTCOM, RADBNo ROA
212.95.148.0/23NTTCOM, RADBNo ROA
212.95.149.0/24NTTCOMNo ROA
212.95.150.0/23NTTCOM, RADBNo ROA
212.95.150.0/24NTTCOMNo ROA
212.95.152.0/21NTTCOM, RADBNo ROA
212.95.152.0/22NTTCOM, RADBNo ROA
212.95.152.0/23NTTCOM, RADBNo ROA
212.95.154.0/23NTTCOM, RADBNo ROA
212.95.156.0/22NTTCOM, RADBNo ROA
212.95.156.0/23NTTCOM, RADBNo ROA
212.95.158.0/23NTTCOM, RADBNo ROA
223.130.8.0/22NTTCOMNo ROA

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.