Loading…
Whether each governed benchmark published its most recent close. Read from the committed ledger — the same files the API and the methodology pages read. Free and unauthenticated, like every W.E.T. benchmark value.
2026-08-21 — 4 of 4 benchmarks settled.
| Benchmark | State | Last row | Printed |
|---|---|---|---|
| WETGRI W.E.T. Geopolitical Risk Index | Printed | 2026-08-21 | 16/16 |
| WETFED W.E.T. Fed Path Index | Refused empty-roster | 2026-08-21 | 14/15 |
| WETX World Event Uncertainty Index | Refused min-weight-coverage | 2026-08-21 | 9/15 |
| WETFRAG W.E.T. Fragmentation Index | Refused min-constituents | 2026-08-21 | 12/15 |
Printed — a value was published for that date.
Refused — the index ran, declined to print, and said why. This is the methodology working, not an outage: a published floor was not met, so no number was published rather than a number computed on an incomplete basis. The rule that fired is on the row.
Absent — no row at all for a date the family closed. A hole: nothing published, and nothing saying why. Absences are handled under the incident process and are never backfilled — the close computes from live market state, so re-running it later would print a different number, which is a restatement rather than a repair.
Availability is published as a measured record, not an SLA — see the data licence. A benchmark is not something anyone can put money into: there is no fund, no product and no account behind these numbers.