ResearchRouting table, RPKI, IRR & looking glass

AS32027 Port of Seattle

AS32027 (POS-ASN) is registered to Port of Seattle in US. It originates 5 prefixes in the global routing table.

5
IPv4 prefixes
0
IPv6 prefixes
3,072
IPv4 addresses
0%
RPKI valid

Who holds AS32027

Names from RIPE NCC’s daily list of every allocated AS number. The ASN lookup fetches the full WHOIS record live.

AS number
AS32027
Handle
POS-ASN
Organization
Port of Seattle
Country
US
ASPA
None published

What AS32027 announces

Prefixes originated by AS32027 in the routing table our collectors hold (kept current as routes change), each checked against the RPKI (every ten minutes) and the IRR (daily).

IPv4 prefixes
5
IPv6 prefixes
0
IPv4 addresses
3,072 (12 /24s)
RPKI valid
0 0%
RPKI invalid
0
RPKI not found
5
ROAs naming AS32027
0
With an IRR route object
3 60%

Announced prefixes

Each opens its own page: who announces it, the paths our collectors see, its ROAs and route objects.

IPv4 (5)

RPKI valid   RPKI invalid   no ROA covers it

Who AS32027 buys transit from

Inferred from the AS paths in the RouteViews tables and our own collectors’ feeds, refreshed every 4 hours, most-seen first. 3 upstreams.

Who buys transit from AS32027

None seen: AS32027 does not appear to provide transit to anyone.

Routing registry objects

From the mirrored IRR databases (RADB, the five RIRs and more). Look it up live.

Sourceas-nameMaintained by
NTTCOMPOS-ASNMAINT-ADHT
RADBPORT-1MAINT-AS32027

Route objects with origin AS32027: RADB 4 · NTTCOM 2

as-sets that list AS32027 (5)