Skip to main content

AS394018

ARIN-PFS-SEA

ARIN Operations

Registry

Authoritative registration data

AS number
394018
Name
ARIN-PFS-SEA
Organisation
ARIN Operations
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS394018
199.5.26.0/24 IPv4 /24 not checked
2001:500:a9::/48 IPv6 /48 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS394018
Address families
SIX Seattle: MTU 1500 1,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS394018 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS394018 in AS paths

Observed upstreams
Families
AS174 COGENT-174 265 844
v4 v6
AS6461 ZAYO-6461 189 391
v4 v6
AS8220 COLT 3 3
v4 v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS394018 in AS paths

Observed downstreams
Families
AS53535 ARIN-PFS-ANYCAST 116 585
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 4
v4 v6
AS49544 i3Dnet 1 4
v4 v6
AS1828 UNITAS 1 1
v6
AS18106 VIEWQWEST-SG-AP 1 1
v4

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.