Product1 distinct publisher3 min readPublished
The cable is AWS's project, but the landing station and backhaul at Ocean Shores belong to Toptana, a Quinault Indian Nation company that aimed to be live in 2025 and is only now breaking ground. Nothing carries traffic until 2029.
The Product Desk · Product desk

Compiled by The Product DeskSomething wrong?How this is made
The 420Tbps headline figure doesn't say much on its own about whether replication lag improves between a Tokyo region and a US West region. Divide the headline figure by the fibre count and you get 21Tbps per pair [13], which describes what the system is engineered to carry over its life, not a queue anyone is standing in. Lag comes from the path, and the path is the part AWS has not published. The Japanese end is unspecified, characterised only as providing "geographical diversity relative to traditional cable corridors", with an image that DCD reads as pointing to Tokyo [6].
The more useful detail is who owns the ground. The cable is AWS's project, while the landing station and backhaul at Ocean Shores belong to Toptana Technologies, founded in 2022 and owned by the Quinault Indian Nation, which holds roughly 210,000 acres including 27 contiguous miles of Washington coast [4][7][17]. Assured Communications is program manager and long-term operations provider for the station [8]. Amazon's David Selby, its director of global network planning and acquisition, said resilient high-capacity connectivity "requires trusted infrastructure partners and a long-term commitment to the communities where that infrastructure is developed" [12]. Read plainly: the cloud buys the transport and contracts for the door.
That door has been slow. Toptana announced the station in 2022, hoping to break ground in 2023 and open in 2025 with 1MW across 17,700 sq ft [9]. Groundbreaking has only now happened [5], and the first system through it carries nothing until 2029 [1], four years past that original launch date [16]. AWS bills the cable as the first international system to land in Washington in nearly 30 years [3]; the previous two landed in 1999, one of them the US-Japan PC-1 at Harbour Pointe [10], which puts 30 years between the two Japan routes [14]. Coastline and permits set this clock.
An operator building its own cable is supposed to turn up later as a smaller egress line and a shorter hop. The announcement contains a route, a date, a partner list, and a name the Quinault granted AWS permission to use [11]; DCD's account of it carries no price, no latency figure, and no terms for anyone else's traffic [18]. Owning transport lowers the operator's cost of moving bits. Whether any of that reaches a customer invoice is a pricing decision taken by different people at a different time.
First, whether you can name the cable and the landing station your cross-Pacific traffic uses today, because diversity you cannot trace is diversity you cannot claim in a resilience review. Second, whether any commitment you would make on the strength of a 2029 cable is reversible before 2029. Third, who stands between the beach and the region in your own contract, since on this route that is Toptana's station and Assured's operations team [4][8], which is a different set of numbers to call than a region incident.
Ranked by verification strength, evidence, and original report placement.
AWS announced Sta'O'Nuk, a subsea cable connecting Washington in the US to an unspecified location in Japan, expected to be operational in 2029.
The Sta'O'Nuk cable will offer 420Tbps of capacity across 20 fiber pairs.
The cable is billed as the first international subsea cable to land in Washington state in nearly 30 years.
Amazon is partnering with Toptana Technologies on the Washington portion of the project, which will provide the cable landing station and backhaul network services.
Toptana has broken ground on a new cable landing station in Ocean Shores, Washington, designed to accommodate up to four subsea cable systems, which the company says is the first new CLS in Washington in more than 25 years.
Details of the Japanese landing have not been shared; an image shared by Amazon suggests Tokyo, and Amazon would only say the Japan landing point will "provide geographical diversity relative to traditional cable corridors".
Distinct publishers with included, body-backed reporting in this cluster.
1 article · September 2, 2026
Follow any of these and your For You feed starts watching them — no settings page required.
build
Force the tool call, then hand Lightsail a long-lived key1 distinct publisher
build
CSA's 2026 threat list is a flat line, so ask which threats a config snapshot can prove1 distinct publisher
build
CSPM ends up as the intake queue for agent-provisioned infrastructure1 distinct publisher
build
Axonius runs one agent per tenant on AgentCore, and tracks model cost the same way1 distinct publisher
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Two releases, one outlet
Every load-carrying figure — 420Tbps, 20 pairs, four station slots, the 2029 date — originates with AWS or Toptana and reaches us through a single trade outlet. Nothing has been checked against a permit filing, a marine survey, a supplier contract or a Japanese counterparty. The verifiable parts are the ones DCD went and got: Amazon's refusal to name the Japanese landing, and Toptana's own 2022 documents showing a 2025 launch it no longer claims.
Concrete, not traffic
Something physical has happened — earth is moving at Ocean Shores, and Assured is contracted through long-term operations — so this is more than a press release. But the station holds four systems and exactly one is named, that one carries nothing until 2029, and no third party has committed to the other three slots. Adoption here means one anchor tenant on a facility that missed its first launch date by four years.
Superlatives dated 2029
'First in nearly 30 years' and '420Tbps' are doing the work of a live asset here, and the asset is three years out on a station that is four years late. The naming ceremony and the two firsts — first international landing in three decades, first Indigenous-owned landing station on the coast — are all true and all announcement-stage. DCD's own framing pushes back, which keeps the gap moderate rather than wide.
Three partners, three quotes
Amazon, Toptana and Assured each get a quote, and each has the same thing to gain: Amazon signalling Pacific resilience and community partnership, Toptana marketing three empty slots to future cable owners, Assured advertising itself as the firm that gets landing stations built. The Quinault Nation's grant of the Sta'O'Nuk name is a genuine cultural act and also, unavoidably, brand. No party in the story has an interest in dwelling on the 2025 date that came and went.
Facts firm, scrutiny thin
We are confident about what was announced and by whom; the paper trail on a groundbreaking and a named cable system is hard to get wrong. We are much less confident that the announced shape survives to 2029 — one publisher, no independent verification, no permits sighted, and a partner with a documented history of missing its own dates. Read the announcement as solid and the schedule as provisional.