bgpreport

Network · data from 2026-11-12

AS21767 WASHINGTON-COLLEGE - Washington College

Registry name: WASHINGTON-COLLEGE - Washington College, US · not in PeeringDB

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

Announced routes

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

192.146.226.0/24 No ROA Other origin only 670 100% 68
209.243.32.0/21 No ROA RIR databaseARIN 672 100% 68
209.243.40.0/21 No ROA RIR databaseARIN 672 100% 68
209.243.32.0/24 No ROA RIR databaseARIN 670 100% 68
209.243.33.0/24 No ROA RIR databaseARIN 670 100% 68
209.243.34.0/24 No ROA RIR databaseARIN 670 100% 68
209.243.35.0/24 No ROA RIR databaseARIN 670 100% 68
209.243.39.0/24 No ROA RIR databaseARIN 670 100% 68
209.243.40.0/24 No ROA RIR databaseARIN 670 100% 68
209.243.41.0/24 No ROA RIR databaseARIN 670 100% 68
209.243.42.0/24 No ROA RIR databaseARIN 670 100% 68
209.243.44.0/24 No ROA RIR databaseARIN 670 100% 68
209.243.46.0/24 No ROA RIR databaseARIN 670 100% 68
209.243.47.0/24 No ROA RIR databaseARIN 670 100% 68
76.78.85.0/24 No ROA RIR databaseARIN, RADB 666 99% 68

AS-SET

AS21767 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 22 are in fix.csv.

  • ROA: none15
  • Route object: none1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none192.146.226.0/24No ROA covers it. Add a ROA for AS21767, maxLength 24.670 of 673
Route object: none192.146.226.0/24Route objects for it name AS198949. Add a route object with origin AS21767 in the RIR database for the space.670 of 673
ROA: none209.243.32.0/21No ROA covers it. Add a ROA for AS21767, maxLength 21.672 of 673
ROA: none209.243.40.0/21No ROA covers it. Add a ROA for AS21767, maxLength 21.672 of 673
ROA: none209.243.32.0/24No ROA covers it. Add a ROA for AS21767, maxLength 24.670 of 673
ROA: none209.243.33.0/24No ROA covers it. Add a ROA for AS21767, maxLength 24.670 of 673
ROA: none209.243.34.0/24No ROA covers it. Add a ROA for AS21767, maxLength 24.670 of 673
ROA: none209.243.35.0/24No ROA covers it. Add a ROA for AS21767, maxLength 24.670 of 673
ROA: none209.243.39.0/24No ROA covers it. Add a ROA for AS21767, maxLength 24.670 of 673
ROA: none209.243.40.0/24No ROA covers it. Add a ROA for AS21767, maxLength 24.670 of 673
ROA: none209.243.41.0/24No ROA covers it. Add a ROA for AS21767, maxLength 24.670 of 673
ROA: none209.243.42.0/24No ROA covers it. Add a ROA for AS21767, maxLength 24.670 of 673
ROA: none209.243.44.0/24No ROA covers it. Add a ROA for AS21767, maxLength 24.670 of 673
ROA: none209.243.46.0/24No ROA covers it. Add a ROA for AS21767, maxLength 24.670 of 673
ROA: none209.243.47.0/24No ROA covers it. Add a ROA for AS21767, maxLength 24.670 of 673
ROA: none76.78.85.0/24No ROA covers it. Add a ROA for AS21767, maxLength 24.666 of 673

Route objects not announced

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

209.243.32.0/20ARINNo ROA
209.243.36.0/24ARINNo ROA
209.243.37.0/24ARINNo ROA
209.243.38.0/24ARINNo ROA
209.243.43.0/24ARINNo ROA
209.243.45.0/24ARINNo 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.