Where the data comes from
Match details are requested by this site’s server from the Sportmonks Cricket API v2 using a protected token. The browser receives only names, status, score, venue and timestamps. It never receives the provider token or a provider request URL. Available fields depend on the source record; this attribution is not a claim of complete coverage or official match reporting.
What is stored
Validated, normalized match snapshots are held in the managed database cache. A provider ID, real team names and a valid start timestamp are required before a record is shown. Any absent field stays absent; no score, winner, venue or line-up is inferred.
How often a check happens
- Visible scoreboards generally check our server every five seconds during verified active play and every 30 seconds otherwise. The shared live-feed provider cache is reused for about ten seconds during active play or 60 seconds when no match is active; a browser check does not always make a new provider request.
- Upcoming fixtures and recent results are reused in the shared provider cache for about three minutes. Full listings check our server about every 60 seconds while visible; the displayed successful source-check time remains unchanged until the source is checked again.
- Provider throttling triggers backoff, during which earlier source checks remain labelled delayed. Browser tabs do not keep checking while hidden. This site has no persistent background refresh when no one is viewing it.
- Match detail is usually served from a verified cached record; an expired or missing exact fixture can trigger a bounded source check. Verified finished snapshots may also be read from the optional archive. An archived result is not a newly checked live update.
Late, missing or unconfirmed data
A fresh live label requires a provider in-play state and a successful site check in the last two minutes. If a check fails, the last verified snapshot is marked delayed; if nothing is available, the page says so. Finished results require the provider’s Finished status. Unknown statuses are not called live.
Scope and calculations
The schedule covers the next ten days in the authorised provider feed. Public result and statistics listings remain a rolling five-day window. A separate, resumable import stores up to 24 months of real decided results for an independent, experimental Elo-like model; model comparisons appear on FairPlay Live with their own history and quality context. Teams begin at 1500, with a disclosed K-factor of 24, logistic scale of 400 and first-named-side adjustment of 30. No winner estimate appears below eight rated matches per team, and estimates are shrunk toward 50% until 20. These assumptions are not the undisclosed reference engine.
The read-only rate prototype uses the reference’s proposed, unapproved 105% two-sided margin, a separately disclosed 0.01 decimal ladder, short expiry and fail-closed suspensions. No money, Pick Slip or betting action is active. History import is a finite TypeScript command, not a claim of continuous background ingestion.
External back and lay quotes
The FairPlay Rates table uses the separate owner-supplied external rate endpoint, not Sportmonks or the in-house model. Each price is paired with its own source-listed size. The visible board checks a bounded server cache about every 15 seconds. Its time is our last successful fetch, not an upstream quote-generation timestamp. Missing, suspended or failed-source quotes are withheld; the table has no stake submission, wallet debit or wager.
Publisher and editorial context
About FairPlay explains the site’s sports-information purpose. Read the editorial policy and content standards for source and article labels. To flag a problem, use the corrections process and contact form with the page URL and the relevant source.
These are sports-information records only. Use them responsibly.