bgpreport

Network · data from 2026-11-12

AS1798 State of Oregon

Registry name: OREGON - State of Oregon, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS1798, 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.234.56.0/24 No ROA Other IRR onlyALTDB, RADB 669 99% 68
198.232.200.0/24 Valid Nonecovered by 198.232.200.0/22 2 0%low visibility 2
198.232.202.0/24 Valid Nonecovered by 198.232.200.0/22 2 0%low visibility 2
199.48.32.0/20 Valid RIR databaseARIN 673 100% 68
159.121.0.0/16 Valid RIR databaseARIN 670 100% 68
167.131.0.0/16 Valid RIR databaseARIN 670 100% 68
170.104.0.0/16 Valid RIR databaseARIN 670 100% 68
192.84.215.0/24 Valid RIR databaseARIN 670 100% 68
192.149.16.0/24 Valid RIR databaseARIN 670 100% 68
192.152.7.0/24 Valid RIR databaseARIN 670 100% 68
198.176.0.0/21 Valid RIR databaseARIN 670 100% 68
198.176.229.0/24 Valid RIR databaseARIN 670 100% 68
198.177.16.0/21 Valid RIR databaseARIN 670 100% 68
198.177.24.0/22 Valid RIR databaseARIN 670 100% 68
198.232.198.0/23 Valid RIR databaseARIN 670 100% 68
198.232.200.0/22 Valid RIR databaseARIN 670 100% 68
198.252.231.0/24 Valid RIR databaseARIN 670 100% 68
199.74.0.0/21 Valid RIR databaseARIN 670 100% 68
204.58.240.0/22 Valid RIR databaseARIN 670 100% 68
205.143.224.0/21 Valid RIR databaseARIN 670 100% 68
205.167.156.0/23 Valid RIR databaseARIN 670 100% 68
205.235.192.0/20 Valid RIR databaseARIN 670 100% 68
2001:580::/32 Valid RIR databaseALTDB, ARIN 635 100% 70
2607:6d00::/32 Valid RIR databaseARIN 635 100% 70

AS-SET

AS1798'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 12 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none192.234.56.0/24No ROA covers it. Add a ROA for AS1798, maxLength 24.669 of 673
Route object: RIR192.234.56.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
Route object: none198.232.200.0/24No route object for it. A route object for 198.232.200.0/22 with origin AS1798 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1798 in the RIR database for the space.2 of 673
Route object: none198.232.202.0/24No route object for it. A route object for 198.232.200.0/22 with origin AS1798 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1798 in the RIR database for the space.2 of 673

Route objects not announced

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

192.136.62.0/24ARINValid
192.146.205.0/24ARINValid
198.177.16.0/22ARINInvalid: maxLength
198.177.20.0/22ARINInvalid: maxLength
198.252.211.0/24ARINValid
204.144.80.0/24ARINValid
2602:808:6000::/40ARINNo ROA
2620:1f0::/32ALTDB, ARINNo 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.