Native UALink switch ASICs announced as samplingno data
— count
on track <= 1 · off >= 2manual ↗
connector returned no usable reading · checked 2026-10-19
Radar · Networking fabric · T1 · 2027 · WARNING
No UALink Consortium member announces general availability or volume production of a switch ASIC implementing the native UALink 200G specification (not an Ethernet-tunnelled or bridged variant) on or before 2027-12-31.
Scale-up fabric is where NVLink's moat lives. Until a native UALink switch ships in volume, every non-NVIDIA accelerator rack is bridged over Ethernet with a latency and power penalty, which caps how fast custom silicon can take share. Rack power density and cabling design for 2028 buildings depend on which fabric actually exists.
Registered at 50% on September 8, 2026. Engine repriced 14 times; now 45%.
Registered thresholds. Status is computed from the latest public reading.
Native UALink switch ASICs announced as samplingno data
— count
on track <= 1 · off >= 2manual ↗
connector returned no usable reading · checked 2026-10-19
Second non-Broadcom vendor cites 1.6T or CPO hyperscaler design winno data
— boolean
on track == 0 · off == 1manual ↗
connector returned no usable reading · checked 2026-10-19
Would raise my number
Would cut it
6 personas on one model (openai/gpt-5.6-sol); other vendors were unavailable this run, so read this as one model's persona-averaged view.
44%
grid-and-power-planner · openai/gpt-5.6-sol
Reference class: sampled merchant data-center switch ASICs approaching a stated product year. I assign roughly a 0.50 annual hazard of a qualifying production announcement; compounded over about 14 months, that implies approximately 0.56 probability of MISS and 0.44 of HIT. The supplied sampling status and 2027 roadmap make shipment plausible, while qualification, firmware, ecosystem, and packaging delays support slippage. The resolution’s native-UALink and explicit production-language requirements exclude demonstrations, sampling, and Ethernet bridges. With both indicators returning no data, there is no evidence strong enough to move materially from that base rate.
44%
semiconductor-supply-chain-analyst · openai/gpt-5.6-sol
Reference class: sampled leading-edge networking ASICs typically require roughly 12–18 months for qualification, software maturity, customer validation, and production ramp. With about 14 months remaining, slippage risk is substantial. However, the public roadmap targets products in 2027, native silicon is reportedly already sampling, and the claim requires every consortium member to avoid a qualifying announcement. Multiple potential suppliers plus the low bar of an official “volume production” statement reduce the survival probability. The strict native-200G and specified-source requirements provide some offset because bridge products, demonstrations, and sampling do not count. Missing indicator data adds no positive evidence. My estimate is slightly below the structural prior and the forecaster’s 0.50.
44%
enterprise-cio · openai/gpt-5.6-sol
I use the reference class of new datacenter interconnect ASICs progressing from sampling to a qualifying production announcement, typically within 9–18 months when ecosystem products are already targeted for the following year. From the supplied September 2026 sampling status, I estimate roughly a 0.52 annual hazard of at least one member issuing qualifying language. Compounded over about 15 months, that leaves approximately 0.44 survival probability for no announcement. Integration and customer qualification favor slippage, but only one member must publish, and the rule’s ambiguity treatment lowers the thesis probability. The estimate is slightly below both the 0.4605 structural prior and stated 0.50.
47%
credit-analyst · openai/gpt-5.6-sol
Using new interconnect/switch ASIC sampling-to-volume transitions as the reference class, I assign roughly a 0.47 annual hazard of a qualifying production announcement. Over the remaining 14.5 months, roadmap pressure and multiple consortium members raise cumulative falsification risk above one-half. Against that, native UALink requires new silicon and ecosystem validation, while the supplied September 2026 state still describes sampling and bridge-based deployments. The strict wording excludes demonstrations, early access, design wins, and Ethernet-tunnelled products. Both indicators returned no data, so they provide no positive update. My estimate is close to, but slightly below, the forecaster’s 0.50 and the 0.4605 structural prior.
44%
geopolitics-policy-analyst · openai/gpt-5.6-sol
Reference class: sampled datacenter switch ASICs targeting products within roughly 12–18 months. With several consortium members able to commercialize silicon, the compounded chance that at least one reaches production and issues qualifying language by end-2027 is slightly above one-half. Against that, native UALink is a new fabric, bridge-based deployments can defer native switching, and sampling does not establish production readiness. The strict channel and wording requirements raise the HIT probability, but ambiguity resolving against the forecaster offsets part of that advantage. This is modestly below the 0.4605 disclosure prior and the forecaster’s 0.50.
43%
superforecaster-statistician · openai/gpt-5.6-sol
Base rate: the engine’s disclosure-question reference class gives 0.4605 for no qualifying announcement. I adjust upward slightly because native switch silicon reportedly remained at sampling in September 2026, deployments used bridges, and volume production requires further validation. I adjust downward more because roughly 14 months remain, the consortium roadmap targets products in 2027, and resolution requires only one member’s production-status announcement—not independently verified volume shipments. Ambiguity also resolves against the thesis. The missing indicator data provides no additional support. Net: a qualifying announcement is modestly more likely than not, so the statement is slightly below the structural prior.
46% from reference-class:qtype:disclosure. ledger base rate, n=37, horizon 438d; the ledger has no multi-year history