Frequently Asked Questions
Answers to the things people ask us most.
- What is Cricket Metrix?
- Cricket Metrix is a read-only cricket statistics site covering leagues, teams, fixtures, results, scorecards, standings, and stats. No fantasy, no betting slips, no accounts — just match data.
- Where does the data come from?
- Match data (fixtures, results, scorecards, standings, odds) comes from api-cricket.com. Player biographies and career stats come from cricketdata.org. Both pipelines ingest into a Supabase Postgres database that this site reads from directly.
- How often is the data updated?
- Live matches update every ~30 seconds. Finished matches, fixtures, and standings refresh on a longer schedule — typically within 5–15 minutes of upstream updates.
- Why don't some leagues have standings?
- Our upstream data provider doesn't populate a real standings endpoint for several flagship T20 leagues (BBL, WBBL, PSL, BPL, CPL, ILT20, SA20, The Hundred, T20 Blast, domestic first-class). For those, we compute standings ourselves from finished match results and mark the table with a 'derived from match results' badge.
- Why aren't player names clickable?
- Our two data sources use different player identity systems — scorecards have free-text player names, while player biographies have UUID-based IDs that don't reliably match. Rather than link player names to the wrong profile, we render them as plain text.
- What formats and competitions do you cover?
- T20, ODI, Test, The Hundred, and T10 — every currently active men's, women's, international, and domestic cricket competition we can pull from upstream. Historical seasons before 2025 aren't backfilled yet.
- Do you have live ball-by-ball commentary?
- No. Our upstream feed no longer includes commentary text, so we don't show it rather than fake it. For live matches we show run rate, status line, and current innings progress.
- I found a data error — how do I report it?
- Email us at hello@cricketmetrix.com with the URL of the page and a description of what's wrong. We can't always fix upstream issues, but we track them and will note known gaps where we can.