bgpreport

Network · data from 2026-11-12

AS13409 Internetworks

Registry name: PDX - PORTLAND INTERNETWORKS, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13409, 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.64.224.0/24 Invalid: maxLength Nonecovered by 69.64.224.0/20 1 0%low visibility 1
69.64.225.0/24 Invalid: maxLength Nonecovered by 69.64.224.0/20 1 0%low visibility 1
69.64.226.0/24 Invalid: maxLength Nonecovered by 69.64.224.0/20 1 0%low visibility 1
69.64.228.0/24 Invalid: maxLength Nonecovered by 69.64.224.0/20 1 0%low visibility 1
69.64.224.0/20 Valid RIR databaseARIN 671 100% 67
2604:c300::/32 Valid RIR databaseARIN 636 100% 67
76.76.144.0/20 Valid RIR databaseARIN 3 0%low visibility 3

AS-SET

AS13409'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 8 are in fix.csv.

  • ROA: maxLength4
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: maxLength69.64.224.0/24ROA 69.64.224.0/20 AS13409 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 69.64.224.0/24.1 of 673
Route object: none69.64.224.0/24No route object for it. A route object for 69.64.224.0/20 with origin AS13409 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13409 in the RIR database for the space.1 of 673
ROA: maxLength69.64.225.0/24ROA 69.64.224.0/20 AS13409 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 69.64.225.0/24.1 of 673
Route object: none69.64.225.0/24No route object for it. A route object for 69.64.224.0/20 with origin AS13409 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13409 in the RIR database for the space.1 of 673
ROA: maxLength69.64.226.0/24ROA 69.64.224.0/20 AS13409 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 69.64.226.0/24.1 of 673
Route object: none69.64.226.0/24No route object for it. A route object for 69.64.224.0/20 with origin AS13409 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13409 in the RIR database for the space.1 of 673
ROA: maxLength69.64.228.0/24ROA 69.64.224.0/20 AS13409 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 69.64.228.0/24.1 of 673
Route object: none69.64.228.0/24No route object for it. A route object for 69.64.224.0/20 with origin AS13409 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13409 in the RIR database for the space.1 of 673

Route objects not announced

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