TCI‑CRI‑H100$3.49TCI‑CRI‑H100‑7D$3.35TCI‑CRI‑H100‑MKT— GAPTCI‑CRI‑COMPUTE107.4TCI‑CRI‑H100$3.49TCI‑CRI‑H100‑7D$3.35TCI‑CRI‑H100‑MKT— GAPTCI‑CRI‑COMPUTE107.4TCI‑CRI‑H100$3.49TCI‑CRI‑H100‑7D$3.35TCI‑CRI‑H100‑MKT— GAPTCI‑CRI‑COMPUTE107.4
AS OF 2026-09-17 20:32:22 UTC

Intake

1979 observations were collected for the 17 Sep 2026 session. 75 of them reached the calculation, 3.8%. 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
82841.8%the panel does not admit this provider, through this collector, in this classnot_in_panel
63932.3%a GPU the index does not price, or a variant that is not the reference unit of its classnot_a_reference_variant
25012.6%spot, interruptible or community capacity, which the unit excludestier_excluded
914.6%sold outside the region block being priced, or with no country recorded at alloutside_block
854.3%a term-committed price, not the on-demand reference unitterm_not_reference
753.8%reached the calculationadmitted
110.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
gpuhunt1291241.9%the panel does not admit this provider, through this collector, in this class
azure_retail2943411.6%a GPU the index does not price, or a variant that is not the reference unit of its class
ovh11000.0%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
hyperstack3000.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_ai26726.9%spot, interruptible or community capacity, which the unit excludes
digitalocean2300.0%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
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
seeweb
no route to a print
400.0%the panel does not admit this provider, through this collector, in this class
static_yaml33100.0%

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.

Not yet measurable

Both checks compare this session against earlier ones, and no session has a stored ledger yet. The next daily run recovers the record from the observations already held, and both checks report from that run onwards.

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.

No sessions recorded yet

The ledger is written by the daily run, which also recovers any session it has no record of. The first run after this table was created fills it with the whole record at once.