GPU price & market log: October 2026, page 2
Entries dated Oct 11 – Oct 14, with their full explanation, source evidence and permanent links. October 2026 runs to 2 pages.
37 of 72 entries in October 2026, page 2 of 2 · Source archives through .
Browse all 96 entries by month
Each month contains its complete record. Month links open with fresh filters.
Newest entriesFilters apply to this page. Corrections use their recording dates; later market milestones are marked Scheduled when they fall after the source archives.
Event date range
Inclusive event dates, which can differ from evidence or archive snapshot dates.
Showing 37 of 37 events on this page
Anchor move up H200 anchor repriced +5.8% between sessionsH200
$5.49 (2026-10-13) → $5.81 (2026-10-14) on the same monthly-average instrument (KXH200MS · KXH200MS-26OCT) under one methodology (threshold ±5%).
Derived from archived curve sessions 2026-10-13 · 2026-10-14 · Data: Kalshi (KalshiEX LLC)
Withdrawn entry B300 marketplace floor entry withdrawn: it was computed from Vast.ai pricesB300 · marketplace floor
Vast.ai marketplace prices were withdrawn on 2026-10-20: Vast's terms bar their use in price comparisons. This entry was computed from those prices, so it was withdrawn with them.
Permalink for B300 marketplace floor entry withdrawn: it was computed from Vast.ai prices
Withdrawn entry H100 marketplace floor entry withdrawn: it was computed from Vast.ai pricesH100 · marketplace floor
Vast.ai marketplace prices were withdrawn on 2026-10-20: Vast's terms bar their use in price comparisons. This entry was computed from those prices, so it was withdrawn with them.
Permalink for H100 marketplace floor entry withdrawn: it was computed from Vast.ai prices
Correction Correction: Cluster-ledger dates, an unsourced chip count and two citations were wrongBuildout
Was: The cluster ledger dated Stargate Saline's announcement to Jun 1, 2026 and Reliance Jamnagar's to Jan 2025, gave Stargate Abilene ~450K GB200/GB300-class accelerators with no source behind the figure, and cited the wrong sources for claims on Fairwater Wisconsin and Stargate Argentina. Corrected to: Stargate Saline's announcement was dated Oct 30, 2025 and Jamnagar's Aug 29, 2024; Abilene was given ~403K B200/B300 projected at full buildout, labeled as a tracker estimate; and both claims were given their own sources. Where: /buildout cluster ledger; buildout.json. Found by a scheduled survey.
Evidence: Cluster ledger with each claim's source · Full record
Permalink for Correction: Cluster-ledger dates, an unsourced chip count and two citations were wrong
Correction Correction: Microsoft's 2023 capex was understatedFinancials
Was: Microsoft's calendar-2023 capital expenditure read $41.0B. Corrected to: $41.2B, the sum of Microsoft's four quarterly investor-relations figures, finance leases included. Where: /buildout capex chart and table; homepage capex chart and table. Found by a scheduled survey.
Evidence: Capex table on /buildout · Full record
Permalink for Correction: Microsoft's 2023 capex was understated
Correction Correction: Two desk-log entries read a venue change and a partial archive as price recordsGPU quotes
Was: The desk log said “RTX 4090 floor cut −38.5%”, but Salad's lower tier had entered the comparison while Vast.ai's price rose. It also said “B200 floor at $6.25 — lowest in the archive's 81-day span”, but the daily price ledger shows $4.19 on Aug 5, 2026. Corrected to: The log was changed to record a changed venue set as a venue change with its like-for-like move, and to claim a floor low only when the full daily ledger holds nothing lower in its span. The RTX 4090 entry became a venue change; the B200 floor-low entry was withdrawn. Where: /log; RSS feed. Found by a review of published pages and data. Corrected again on Oct 20, 2026: Vast.ai marketplace prices were published although Vast's terms bar their use in price comparisons.
Evidence: B200 daily price ledger ($4.19 on Aug 5, 2026) · RTX 4090 daily price ledger · Full record
Correction Correction: Chip-page price ranges hid that an endpoint was an old estimateGPU quotes
Was: Chip pages printed all-market ranges such as “All-market access $1.99 → $6.00” on MI300X without saying that the $1.99 endpoint is a secondary estimate observed on Jul 6, 2026. Corrected to: Ranges were changed to print an estimated endpoint's est flag and its own observation date, so the MI300X range marked $1.99 as an estimate observed on Jul 6, 2026. Where: all-market ranges on the chip pages. Found by a scheduled survey. Corrected again on Oct 20, 2026: Prices from five GPU clouds whose terms bar reuse, and three aggregator estimates, were published.
Evidence: MI300X chip page · Full record
Permalink for Correction: Chip-page price ranges hid that an endpoint was an old estimate
Correction Correction: Year-on-year and streak figures compared unlike seriesGPU quotes
Was: The B200 tile read “+42% y/y”, a change computed by array position across a missing quarter and a methodology change. Streak copy called a single quarter near $3.99 a run of “straight quarters”, and each ticker arrow came from a different series than the value beside it. Corrected to: Changes were made to follow calendar quarters within one methodology and to compare only the venues quoted at both ends; at the correction the B200 tile read “+16.9% like-for-like since Jul 23, 2026”. Streak copy was made to need at least two quarters, and each arrow to come from the series its value shows. Where: homepage B200 tile, lede and brief; market tape arrows; chip mastheads and The Board deltas; /gpu-cloud quote-snapshot read. Found by a review of published pages and data. Corrected again on Oct 20, 2026: Prices from five GPU clouds whose terms bar reuse, and three aggregator estimates, were published.
Evidence: Jul 23, 2026 quote snapshot · Oct 13, 2026 quote snapshot · Full record
Permalink for Correction: Year-on-year and streak figures compared unlike series
Correction Correction: Quotes last observed on Jul 23 were dated to a later surveyGPU quotes
Was: Vast.ai rows last observed on Jul 23, 2026 (H100 $1.73, H200 $3.93 and B300 $8.34 per GPU-hour) were cited with the date of the manual survey (Oct 11) in the H100, H200 and B300 chip-page FAQs and their structured data, and the H100 row also in the homepage lede and brief. Corrected to: Each cited row was given its own observation date (“last observed Jul 23, 2026”), and the chip-page FAQ's cheapest-venue answer was changed to name the cheapest primary on-demand row separately from the marketplace-access floor. Where: H100, H200 and B300 chip-page FAQ and FAQPage JSON-LD; homepage H100 lede and brief; venue-spread tile and notes; /gpu-cloud venue-spread panel. Found by a review of published pages and data. Corrected again on Oct 20, 2026: Vast.ai marketplace prices were published although Vast's terms bar their use in price comparisons.
Evidence: H100 price ledger (Vast.ai $1.73, observed Jul 23) · H200 price ledger (Vast.ai $3.93, observed Jul 23) · B300 price ledger (Vast.ai $8.34, observed Jul 23) · Full record
Permalink for Correction: Quotes last observed on Jul 23 were dated to a later survey
Correction Correction: Three quotes stayed listed after their sources stopped publishing themGPU quotes
Was: Google Cloud (A4) B200 on-demand at $16.11 (est) stayed in the table although Google's pricing page shows no on-demand A4 price, and so did FluidStack H200 at $2.30 (est), although FluidStack publishes no GPU prices, and SF Compute H100 at $2.04, a market price SF Compute no longer publishes. The first two set the B200 all-market ceiling and the H200 all-market floor. Corrected to: All three were retired from the quote table. With the Oct 14, 2026 update, the B200 all-market ceiling became AWS (p6) at $14.24 and the H200 all-market floor Vast.ai at $3.93. Where: B200, H200 and H100 quote tables on /gpu-cloud and the chip pages; B200 and H200 all-market ranges. Found by a scheduled survey. Corrected again on Oct 20, 2026: Vast.ai marketplace prices were published although Vast's terms bar their use in price comparisons.
Evidence: Google Cloud accelerator-optimized pricing (A4 on-demand: N/A) · FluidStack pricing page · Full record
Permalink for Correction: Three quotes stayed listed after their sources stopped publishing them
Correction Correction: Vultr plans that cannot be rented on demand were listed as on-demand quotesGPU quotes
Was: Four Vultr bare-metal plans that Vultr's plans API marks as not deployable on demand, with no locations, were listed as On-demand rows: H100 $2.99, B200 $8.50, MI300X $3.99 and MI355X $2.59 per GPU-hour. They made MI355X the cheapest dense compute on /hardware, set its chip-page title to “from $2.59”, and were the only venue in the daily H100 and B200 specialist medians. Corrected to: The rule became that a Vultr plan counts as on-demand only when Vultr lists it as deployable on demand in at least one location. The four rows were retired from the quote table in the Oct 14, 2026 refresh, and no headline used them after it. Where: H100, B200, MI300X and MI355X quote tables on /gpu-cloud and the chip pages; /hardware price per PFLOP-hour leader; MI355X chip-page title; daily H100 and B200 specialist-median history. Found by a review of published pages and data. Corrected again on Oct 24, 2026: Retired Vultr plans returned as the MI300X and MI355X typical prices.
Evidence: Vultr public plans API (deployability and locations per plan) · Full record
Correction Correction: B200 and Rubin bandwidth came from superseded NVIDIA pagesHardware specs
Was: B200 bandwidth read 8.0 TB/s, the DGX B200 figure, and Rubin read 22 TB/s with NVLink at 3.6 TB/s from older HGX pages, beside an unverified TSMC 3nm node. Corrected to: HGX B200: 7.7 TB/s per GPU, from the HGX B200 column of NVIDIA's Blackwell datasheet. Rubin: 19.2 TB/s and NVLink 6 at 3 TB/s, from NVIDIA's Vera Rubin NVL72 page and datasheet, with no process node because NVIDIA stated none. NVIDIA's own pages disagreed on Rubin at the time, and the chip note said so. Where: /hardware spec table; llms-full.txt accelerator specs; /hardware HBM bandwidth chart. Found by a scheduled survey.
Evidence: NVIDIA Blackwell datasheet (HGX B200 column) · NVIDIA Vera Rubin NVL72 · NVIDIA Vera Rubin datasheet · Full record
Permalink for Correction: B200 and Rubin bandwidth came from superseded NVIDIA pages
Correction Correction: Gaudi 3 throughput used Intel's superseded 2024 figureHardware specs
Was: Gaudi 3 was listed at 1,835 TF dense BF16 and FP8, the figure in Intel's 2024 Hot Chips deck, with a $15,650 list price. Corrected to: 1,678 TF BF16 and FP8, as Intel's July 2025 white paper (Rev. 3) gives at 900 W, and a $15,625 list price ($125,000 per eight-accelerator kit). Where: /hardware spec table; llms-full.txt accelerator specs. Found by a scheduled survey.
Evidence: Intel Gaudi 3 AI accelerator white paper (Rev. 3) · Full record
Permalink for Correction: Gaudi 3 throughput used Intel's superseded 2024 figure
Correction Correction: GeForce tensor throughput used the 2× FP16-accumulate ratesHardware specs
Was: RTX 4090 was listed at 330 TF dense BF16 and 661 TF FP8, and RTX 5090 at 419 TF and 838 TF: NVIDIA's FP16-accumulate rates, twice the FP32-accumulate figures that data-center datasheets give. Corrected to: RTX 4090: 165.2 TF BF16 and 330.3 TF FP8. RTX 5090: 209.5 TF BF16, 419 TF FP8 and 1.68 PF FP4. These are the dense FP32-accumulate rates in NVIDIA's architecture whitepapers, so both cards' rental price per PFLOP-hour doubled. Where: /hardware spec table and price per PFLOP-hour ranking; llms-full.txt accelerator specs. Found by a review of published pages and data.
Evidence: NVIDIA Ada GPU Architecture whitepaper V2.02, Appendix A, Table 2 · NVIDIA RTX Blackwell GPU Architecture whitepaper V1.1, Appendix A, Table 3 · Full record
Permalink for Correction: GeForce tensor throughput used the 2× FP16-accumulate rates
Correction Correction: Smaller hardware fixes: TPU notes, estimate flags, process nodes and a launch monthHardware specs
Was: TPU v5p's note said it trained Gemini 1.0, TPU v5e's gave its INT8 rate as 394 TOPS, and TPU7x's said capacity required a supported reservation. The V100, A100 and H100 street prices ($10,000, $15,000 and $27,500) carried no estimate flag although only secondary sources give them. A100 and RTX 5090 process nodes read TSMC 7N and TSMC 4NP, and MI355X's launch month read Oct 2025. Corrected to: The notes were changed to say that TPU v5p was announced alongside Gemini 1.0, which was trained on TPU v4 and v5e; that v5e INT8 is 393 TOPS; and that TPU7x had been generally available on demand since March 2026, with quota required. The three street prices were flagged as estimates, the nodes changed to TSMC N7 and TSMC 4N, and MI355X's launch month to Sep 2025. Where: /hardware spec table; llms-full.txt accelerator specs; /hardware chip notes. Found by a scheduled survey.
Evidence: Google Cloud TPU v5p · Google Cloud TPU v5e · Google Cloud TPU release notes · NVIDIA A100 specifications · Vendor sources listed with each chip · Full record
Correction Correction: Maia 200 throughput was approximateHardware specs
Was: Maia 200 was listed at 5,000 TF FP8 and 10,000 TF FP4, flagged as estimates. Corrected to: 5,072 TF FP8 and 10,145 TF FP4, the peak-specification table in Microsoft's Maia 200 architecture deep dive. Its BF16 peak is a vector-unit rate, so the tensor BF16 field stayed empty. Where: /hardware spec table; llms-full.txt accelerator specs. Found by a scheduled survey.
Evidence: Maia 200 architecture deep dive (peak-specification table) · Microsoft Maia 200 announcement · Full record
Permalink for Correction: Maia 200 throughput was approximate
Correction Correction: AMD's MI400-series flagship was listed at half its dense throughputHardware specs
Was: The Instinct MI400 row read AMD's figures as sparse and halved them: 10 PF FP8 and 20 PF FP4, with no BF16 rate. It also listed 19.6 TB/s, no board power, announced status and a Dec 2026 launch. Corrected to: The row became the Instinct MI455X: 5,033 TF BF16, 20,133 TF FP8 and 40,265 TF MXFP4, which AMD publishes as dense rates, with 23.3 TB/s of HBM4 bandwidth, 2,500 W board power, ramping status and an estimated Oct 2026 launch. Where: /hardware spec table; llms-full.txt accelerator specs; /hardware HBM bandwidth chart. Found by a scheduled survey.
Evidence: AMD Instinct MI455X specifications · Full record
Permalink for Correction: AMD's MI400-series flagship was listed at half its dense throughput
Correction Correction: Four current OpenAI models were missing from the token-price tableToken prices
Was: The current token-price table, reviewed on Oct 11, 2026, left out GPT-5.6 Sol, Terra and Luna (released Jul 9) and GPT-6 Sol (released Sep 22). Corrected to: All four were added at their Standard prices per million input and output tokens: GPT-6 Sol $2 and $10, GPT-5.6 Sol $4 and $20, GPT-5.6 Terra $2 and $12, and GPT-5.6 Luna $0.20 and $1.20. Where: /inference current price table; llms-full.txt token prices. Found by a scheduled survey.
Evidence: OpenAI GPT-6 Sol model page · OpenAI GPT-5.6 Sol model page · OpenAI GPT-5.6 Terra model page · OpenAI GPT-5.6 Luna model page · Full record
Permalink for Correction: Four current OpenAI models were missing from the token-price table
Market structure Kalshi — No weekly ladder open; monthly ladders openKalshi
Every Kalshi capture this site made from Oct 11 through Oct 14 found no open weekly compute event for any chip, so each anchored on its monthly-average event; those monthly-average ladders stayed open. The capture before that, on Aug 28, listed weekly events for B200, H200, H100 and A100 expiring Sep 4 through Oct 9 (none for RTX 5090). No capture was made in between, so when the weekly events stopped is not on record. Status after: live. Source: This site’s archived Oct 11 session (anchor per chip).
Source: https://aicomputetracker.com/archive/curves/2026-10-11.json
Permalink for Kalshi — No weekly ladder open; monthly ladders open
Venue change B200 typical price: Vultr added between the Jul 23 and Oct 11, 2026 quote snapshotsB200 · typical price
The venue set changed between the Jul 23 and Oct 11, 2026 quote snapshots: Vultr entered at $8.50. The archived typical price moved $6.92 → $8.19 (+18.4%), which is not a like-for-like price change. Like-for-like, the 4 venues quoted in both snapshots moved +7.5% at the median ($6.92 → $7.44).
Derived from archived quote days 2026-07-23 · 2026-10-11
Permalink for B200 typical price: Vultr added between the Jul 23 and Oct 11, 2026 quote snapshots
Withdrawn entry H200 typical price entry withdrawn: it was computed from CoreWeave, Crusoe and RunPod pricesH200 · typical price
CoreWeave prices were withdrawn on 2026-10-20: CoreWeave's terms bar displaying its site's content with services that are not its own. Crusoe prices were withdrawn on 2026-10-20: Crusoe's terms bar copying, publishing or displaying its site's content without written permission. RunPod prices were withdrawn on 2026-10-20: RunPod's terms bar compiling its data into a collection or database without written permission. This entry was computed from those prices, so it was withdrawn with them.
Withdrawn entry RTX 4090 marketplace floor entry withdrawn: it was computed from Vast.ai pricesRTX 4090 · marketplace floor
Vast.ai marketplace prices were withdrawn on 2026-10-20: Vast's terms bar their use in price comparisons. This entry was computed from those prices, so it was withdrawn with them.
Permalink for RTX 4090 marketplace floor entry withdrawn: it was computed from Vast.ai prices
Withdrawn entry RTX 4090 typical price entry withdrawn: it was computed from RunPod pricesRTX 4090 · typical price
RunPod prices were withdrawn on 2026-10-20: RunPod's terms bar compiling its data into a collection or database without written permission. This entry was computed from those prices, so it was withdrawn with them.
Permalink for RTX 4090 typical price entry withdrawn: it was computed from RunPod prices
Withdrawn entry RTX 5090 marketplace floor entry withdrawn: it was computed from Vast.ai pricesRTX 5090 · marketplace floor
Vast.ai marketplace prices were withdrawn on 2026-10-20: Vast's terms bar their use in price comparisons. This entry was computed from those prices, so it was withdrawn with them.
Permalink for RTX 5090 marketplace floor entry withdrawn: it was computed from Vast.ai prices
Withdrawn entry RTX 5090 typical price entry withdrawn: it was computed from RunPod pricesRTX 5090 · typical price
RunPod prices were withdrawn on 2026-10-20: RunPod's terms bar compiling its data into a collection or database without written permission. This entry was computed from those prices, so it was withdrawn with them.
Permalink for RTX 5090 typical price entry withdrawn: it was computed from RunPod prices
Curve sessions 1 forward-curve session archived · week of Oct 5, 2026Forward board
Archived session 2026-10-11 — each at its dated permalink; notable moves are logged separately.
Derived from archived curve sessions 2026-10-11 · Data: Kalshi (KalshiEX LLC)
Permalink for 1 forward-curve session archived · week of Oct 5, 2026
Correction Correction: Oracle's FY27 funding plan was described as new debtFinancials
Was: /buildout said Oracle ran −$23.7B of free cash flow in FY26 and was raising ~$40B more debt. Corrected to: /buildout was changed to report Oracle's own description, each figure beside its source: a ~$40B FY27 funding plan of debt and equity, no further debt issuance expected in calendar 2026, and $20B of common-stock sales completed in FY27 Q1. Where: /buildout financing notes. Found by a review of published pages and data.
Evidence: Oracle FY26 Q4 and full-year results release (funding plan) · Oracle FY27 Q1 results release · Full record
Permalink for Correction: Oracle's FY27 funding plan was described as new debt
Correction Correction: Three AWS Capacity Block quotes cited the On-Demand pricing pageGPU quotes
Was: The B300 (p6-b300), GB200 NVL72 (u-p6e) and Trainium2 (trn2) Capacity Block rows linked AWS's EC2 On-Demand pricing page instead of its Capacity Blocks pricing page. The B300 row showed $11.70 per GPU-hour. Corrected to: They were changed to cite the EC2 Capacity Blocks pricing page, read on Oct 11, 2026: B300 $16.146 and GB200 NVL72 $10.582 per GPU-hour, and Trainium2 $2.235 per chip-hour, each with its instance configuration. Where: B300, GB200 NVL72 and Trainium2 quote tables on /gpu-cloud and the chip pages; llms-full.txt quote table. Found by a scheduled survey.
Evidence: AWS EC2 Capacity Blocks pricing · Full record
Permalink for Correction: Three AWS Capacity Block quotes cited the On-Demand pricing page
Correction Correction: B200 memory per GPU was overstatedHardware specs
Was: B200 was listed with 192 GB of memory per GPU. Corrected to: 180 GB per GPU, as NVIDIA's HGX reference architecture specifies. Where: /hardware spec table; llms-full.txt accelerator specs. Found by a review of published pages and data.
Evidence: NVIDIA HGX reference architecture, components · Full record
Permalink for Correction: B200 memory per GPU was overstated
Correction Correction: B300 specifications did not match NVIDIA's current HGX datasheetHardware specs
Was: B300 was listed with 15 PF dense FP4, 288 GB of memory, 8.0 TB/s and 1,400 W. Corrected to: The HGX B300 column of NVIDIA's datasheet: 13.5 PF dense FP4 (108 PF per eight-GPU system divided by eight), 270 GB, 7.7 TB/s and 1,100 W. GB300 NVL72 lists different per-GPU figures, so the chip note recorded the discrepancy. Where: /hardware spec table; llms-full.txt accelerator specs. Found by a review of published pages and data.
Evidence: NVIDIA Blackwell Ultra datasheet, page 5 · NVIDIA HGX specifications · Full record
Permalink for Correction: B300 specifications did not match NVIDIA's current HGX datasheet
Correction Correction: MI355X throughput used AMD's sparse figuresHardware specs
Was: MI355X was listed at 5 PF dense BF16, 10.1 PF FP8 and 20.1 PF FP4: AMD's sparse throughput, twice the dense rates. Corrected to: 2.5 PF BF16, 5 PF OCP-FP8 and 10.1 PF MXFP4, AMD's explicit dense specifications, so its rental price per PFLOP-hour doubled. Where: /hardware spec table and price per PFLOP-hour ranking; llms-full.txt accelerator specs. Found by a review of published pages and data.
Evidence: AMD Instinct MI355X specifications · Full record
Permalink for Correction: MI355X throughput used AMD's sparse figures
Correction Correction: Rubin throughput was estimated from a sparse package figureHardware specs
Was: Rubin was listed with only an FP4 rate, 25 PF, estimated by halving NVIDIA's ~50 PF NVFP4 inference figure, with 20 TB/s of bandwidth and no BF16 or FP8 values. Corrected to: The individual-GPU table on NVIDIA's HGX page at the time: 4 PF dense BF16, 17.5 PF FP8/FP6 training and 35 PF NVFP4 training, 22 TB/s, and NVLink 6 at 3.6 TB/s. Where: /hardware spec table; llms-full.txt accelerator specs. Found by a review of published pages and data. Corrected again on Oct 14, 2026: B200 and Rubin bandwidth came from superseded NVIDIA pages.
Evidence: NVIDIA HGX specifications · Full record
Permalink for Correction: Rubin throughput was estimated from a sparse package figure
Correction Correction: TPU memory was shown in GB, and published formats were missingHardware specs
Was: TPU v5p, v6e and v7 memory read 95, 32 and 192 GB although Google specifies GiB. FP8 was blank for v5p and v6e, BF16 was blank for v7, and v7 bandwidth read 7.37 TB/s. Corrected to: 95, 32 and 192 GiB; FP8 459 TF (v5p) and 918 TF (v6e); v7 BF16 2,307 TF; and v7 bandwidth 7.38 TB/s (7,380 GB/s), from Google's TPU7x architecture comparison. Where: /hardware spec table; llms-full.txt accelerator specs. Found by a review of published pages and data.
Evidence: Google Cloud TPU7x architecture comparison · Full record
Permalink for Correction: TPU memory was shown in GB, and published formats were missing
Correction Correction: Trainium2 throughput and memory unit were approximateHardware specs
Was: Trainium2 was listed at 650 TF dense BF16 and 1,300 TF FP8, flagged as estimates, with 96 GB of memory. Corrected to: 667 TF dense BF16, 1,299 TF FP8, 96 GiB and NeuronLink v3 at 1.28 TB/s, as AWS's Neuron documentation specifies. Where: /hardware spec table and price per PFLOP-hour ranking; llms-full.txt accelerator specs. Found by a review of published pages and data.
Evidence: AWS Neuron Trainium2 architecture · Full record
Permalink for Correction: Trainium2 throughput and memory unit were approximate
Correction Correction: Trainium3 dense BF16 was half its FP8 figure, not the published rateHardware specs
Was: Trainium3 was listed at 1.26 PF dense BF16, half its 2.52 PF FP8 figure, with no FP4 value and memory in GB. Corrected to: 671 TF dense BF16, 2.517 PF for both MXFP8 and MXFP4, 144 GiB of memory and NeuronLink v4 at 2.56 TB/s, as AWS's Neuron documentation specifies. Where: /hardware spec table; llms-full.txt accelerator specs. Found by a review of published pages and data.
Evidence: AWS Neuron Trainium3 architecture · Full record
Permalink for Correction: Trainium3 dense BF16 was half its FP8 figure, not the published rate
Correction Correction: An April 2026 token-price floor was presented as currentToken prices
Was: The GPT-4-class token-price floor, a benchmark-qualified series that ends in April 2026, was presented as the current cheapest option on the homepage Explore card, the ticker, the FAQ and /inference. Corrected to: Each surface was changed to label it as archived April 2026 history, beside a current token-price table that compares list prices and does not rank model quality. Where: homepage Explore card, ticker and FAQ; /inference price-collapse chart and notes. Found by a review of published pages and data.
Evidence: Current token prices and the archived series · Full record
Permalink for Correction: An April 2026 token-price floor was presented as current
Correction Correction: CME compute futures were still shown as launching Oct 5Market structure
Was: The homepage, the About page and the venue monitor described CME's Silicon Data H100 and B200 rental-index futures as scheduled to launch on Oct 4, 2026, with a first trade date of Oct 5, pending CFTC review. Corrected to: The venue record, and with it the homepage, the About page and the desk log, was changed to say that CME's Sep 28, 2026 notice had postponed the launch pending regulatory review, without a replacement date. Where: homepage futures brief; /about market-structure section and venue monitor; price-signal notes; /log and RSS feed. Found by a review of published pages and data.
Evidence: CME notice, Sep 28, 2026 (launch postponed) · CME clearing notice 26-274 (effective date to be announced) · Full record
Permalink for Correction: CME compute futures were still shown as launching Oct 5