TCI‑CRI‑H100$3.99TCI‑CRI‑H100‑US$3.99TCI‑CRI‑H100‑GLOBAL$3.93TCI‑CRI‑H100‑7D$3.76TCI‑CRI‑H100‑MKT— GAPTCI‑CRI‑COMPUTE122.8TCI‑CRI‑H100$3.99TCI‑CRI‑H100‑US$3.99TCI‑CRI‑H100‑GLOBAL$3.93TCI‑CRI‑H100‑7D$3.76TCI‑CRI‑H100‑MKT— GAPTCI‑CRI‑COMPUTE122.8
AS OF 2026-10-10 12:27:29 UTC

Intake

2087 observations were collected for the 10 Oct 2026 session. 160 of them reached the calculation, 7.7%. This page is the difference, itemised.

A row qualifies for a print only if it clears every rule of the unit definition: the right GPU, a provider the panel admits through the collector that saw it, an on-demand price rather than a term commitment, firm or list capacity rather than spot, a datacenter inside the block being priced, a node at or above the size floor, a currency there is a rate for, and a price inside the band. Most collected rows fail one of those, and most of the time that is the index working rather than failing: a broad catalogue holds a great many GPUs it does not price.

Each row below is attributed to the first rule it failed, so the counts add up to the session exactly. That also means a rule's count is not the number of rows that would print if it were loosened — a row stopped at the panel may be outside the block and spot-priced as well.

Where the session's rows stopped

Every rule, with what it holds and why.

Rows by the first rule they failed
Rows Share Rule Recorded as
65331.3%a GPU the index does not price, or a variant that is not the reference unit of its classnot_a_reference_variant
45621.8%the panel does not admit this provider, through this collector, in this classnot_in_panel
36917.7%sold outside the region block being priced, or with no country recorded at alloutside_block
31615.1%spot, interruptible or community capacity, which the unit excludestier_excluded
1607.7%reached the calculationadmitted
1215.8%a term-committed price, not the on-demand reference unitterm_not_reference
120.6%fewer GPUs than the node-size floorbelow_node_floor

What each collector contributed

A collector at zero is not necessarily broken. Several collect against region blocks that are not published yet, or sit outside the panel on purpose so they can accumulate the history a future constituent needs. Where nothing a collector produces can reach a print at all, that is marked, because the reason is a decision somebody should be making rather than a fact nobody has noticed.

Rows collected and rows admitted, per collector
Collector Collected Admitted Yield Where the rest stopped
gpuhunt13431078.0%the panel does not admit this provider, through this collector, in this class
azure_retail3414011.7%a GPU the index does not price, or a variant that is not the reference unit of its class
ovh11032.7%a GPU the index does not price, or a variant that is not the reference unit of its class
civo8700.0%a GPU the index does not price, or a variant that is not the reference unit of its class
coreweave3400.0%a GPU the index does not price, or a variant that is not the reference unit of its class
hyperstack3400.0%a GPU the index does not price, or a variant that is not the reference unit of its class
lambda_pricing
no route to a print
2800.0%the panel does not admit this provider, through this collector, in this class
vast_ai2414.2%spot, interruptible or community capacity, which the unit excludes
digitalocean2314.3%a GPU the index does not price, or a variant that is not the reference unit of its class
scaleway19526.3%a GPU the index does not price, or a variant that is not the reference unit of its class
latitude1800.0%a GPU the index does not price, or a variant that is not the reference unit of its class
together
no route to a print
800.0%the panel does not admit this provider, through this collector, in this class
crusoe600.0%a GPU the index does not price, or a variant that is not the reference unit of its class
runpod6233.3%a GPU the index does not price, or a variant that is not the reference unit of its class
seeweb4125.0%a term-committed price, not the on-demand reference unit
voltagepark
no route to a print
200.0%sold outside the region block being priced, or with no country recorded at all

What moved

A constituent that was qualifying and has stopped, or a rule holding a materially different number of rows than it held recently. A collector whose rows all fail one rule looks exactly like a collector that is working: the session succeeds, the stored row count rises, and the print survives on the constituents it already had. That is the failure this watches for.

  • vast.ai through vast_ai in the A100 class was reaching the calculation on recent sessions and is not on this one. Its rows now stop at below_node_floor.
  • vast.ai through vast_ai in the H200 class was reaching the calculation on recent sessions and is not on this one. Its rows now stop at not_collected.
  • vast.ai through vast_ai in the H100P class was reaching the calculation on recent sessions and is not on this one. Its rows now stop at below_node_floor.

Collected against admitted

Rows collected each session beside rows that reached the calculation. The two columns moving apart is the ordinary consequence of adding a collector, whose rows are stored for weeks before a methodology version admits them.

Rows collected and admitted, per session
Session Collected Admitted Yield
20 Sep 20261993733.7%
21 Sep 20261979733.7%
22 Sep 202619531527.8%
23 Sep 202619941598.0%
24 Sep 202620071577.8%
25 Sep 202620201587.8%
26 Sep 202620481638.0%
27 Sep 202620361617.9%
28 Sep 202620301597.8%
29 Sep 202620461668.1%
30 Sep 202620541668.1%
1 Oct 202620841607.7%
2 Oct 202620781637.8%
3 Oct 202620971647.8%
4 Oct 202620921678.0%
5 Oct 202620601607.8%
6 Oct 202620731597.7%
7 Oct 202620771597.7%
8 Oct 202620771607.7%
9 Oct 202620721587.6%
10 Oct 202620871607.7%