Skip to main content

AS393968

GOLDKEY-CORPORATION

GoldKey Corporation

Registry

Authoritative registration data

AS number
393968
Name
GOLDKEY-CORPORATION
Organisation
GoldKey Corporation
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

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

Prefixes announced by AS393968
172.85.76.0/24 IPv4 /24 not checked
172.85.77.0/24 IPv4 /24 not checked
172.85.78.0/24 IPv4 /24 not checked
172.85.79.0/24 IPv4 /24 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 AS393968
Address families
HOUIX: Main 100,000 Mbps IPv4 · IPv6
KCIX 100,000 Mbps IPv4 · IPv6
SIX Seattle: MTU 1500 10,000 Mbps IPv4 · IPv6
STLIX: Main 100,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 AS393968 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS393968 in AS paths

Observed upstreams
Families
AS62943 236 1,289
v4
AS7018 54 247
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS393968 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS18106 VIEWQWEST-SG-AP 1 4
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.