bgpreport

Network · data from 2026-11-12

AS3401 City of Seattle - IIT

Registry name: SEATTLE - City of Seattle, Dept. of Admin. Services, US · PeeringDB

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

Announced routes

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

156.74.248.0/21 No ROA Nonecovered by 156.74.0.0/16 673 100% 67
156.74.248.0/22 No ROA Nonecovered by 156.74.0.0/16 673 100% 67
156.74.252.0/22 No ROA Nonecovered by 156.74.0.0/16 673 100% 67

AS-SET

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

  • ROA: none3
  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none156.74.248.0/21No ROA covers it. Add a ROA for AS3401, maxLength 21.673 of 673
Route object: none156.74.248.0/21No route object for it. A route object for 156.74.0.0/16 with origin AS3401 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3401 in the RIR database for the space.673 of 673
ROA: none156.74.248.0/22No ROA covers it. Add a ROA for AS3401, maxLength 22.673 of 673
Route object: none156.74.248.0/22No route object for it. A route object for 156.74.0.0/16 with origin AS3401 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3401 in the RIR database for the space.673 of 673
ROA: none156.74.252.0/22No ROA covers it. Add a ROA for AS3401, maxLength 22.673 of 673
Route object: none156.74.252.0/22No route object for it. A route object for 156.74.0.0/16 with origin AS3401 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3401 in the RIR database for the space.673 of 673

Route objects not announced

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

156.74.0.0/16RADBNo 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.