Loading this page
Every figure on this site is deterministic demonstration data. It is not a live source, not a forecast, and not a recommendation. No wagering market is connected, and nothing here should be acted on.
Service status, source-family health, region availability, incidents and the last successful update for each component.
Each states what is actually known about it, and which task connects real monitoring.
Components with any real signal behind their state.
No monitoring is connected. Nothing is known about these components — which is not the same as knowing they are well.
An incident with no resolution time is still open. It is not closed by going quiet.
The public research interface, served from the Preview deployment.
The only component with any real signal, and that signal is only that the Preview build serves pages.
The upstream racing data providers behind every source family.
No live source is called during Task 000. The source-family health shown elsewhere in this application is demonstration data describing a shape, not a measurement of any real provider.
This component is not making a positive report about itself.
The PostgreSQL store holding canonical race and runner records.
No database is connected. There is nothing to monitor, and no uptime figure is offered — a figure computed over a component that does not exist would be meaningless.
This component is not making a positive report about itself.
Scheduled retrieval, validation and reconciliation of source payloads.
Not implemented. No ingestion run has ever been attempted.
This component is not making a positive report about itself.
The council of models producing probability distributions.
No model exists. Nothing is computed, so nothing has a health state.
This component is not making a positive report about itself.
The gate deciding whether a research output is published, withheld or quarantined.
Nothing is published, because no model produces an output to gate.
This component is not making a positive report about itself.
An incident stays open until it is explicitly resolved. Going quiet does not close it.
Nothing on this site reflects a live system. Every figure is deterministic demonstration data.
Retained rather than cleared. A status page that deleted resolved incidents would always look calm.
In the demonstration data, Singapore carries no card and is listed on the coverage page with the reason it is absent.
While open, interactive elements on the site did not respond. Static markup was served correctly throughout, which is what made the failure hard to see.
Stated rather than left implied by a calm-looking page.
Where this status report came from and how old it is.
When this answer was assembled, and how old the underlying data was when it was. These are separate facts, and showing only the first would let a cached response read as current.
Regions excluded from this answer, each with the recorded reason. An excluded region is a fact about coverage, not an empty space: