DATA TRANSPARENCY

Data source health

Every win, pick and ban rate is linked to its upstream source, rank, day window and most recent successful fetch. This page also shows failed refreshes and community fallback sources. Unverified patch information is not presented as official.

— Rank/window combinations— Healthy scopes— Scopes needing attention— Recent alerts shown
Status checked Not provided. This only reloads monitoring data; it does not force a bulk upstream fetch.

Verify one ranking scope

All ranked metric sources

Hero cards and the tier list use the same rank/window source. The tier score is an MHQ-derived relative ranking; it is not a separate official metric.

RankWindowCoverageProviderRetrievedCache statusPatch

Recent refresh alerts

No recorded refresh-failure alerts. This does not prove upstream data is current; use the timestamps above.

Metric lineage

Win, pick, ban: Moonton GMS ranked-hero feed for each rank and window; if unavailable, Rone Arena mirror or an eligible daily GitHub snapshot is labeled as a fallback. Cache target: 6 hours; expired after 24 hours.

Tiers: Calculated locally from win, pick and ban for exactly the selected rank and window. Role and lane filters change the comparison pool; the resulting tier is not an official Moonton tier.

Matchups: Moonton’s official hero relationship feed (6-hour cache), ranked pair impact (15-minute cache), and MHQ’s documented strategic scoring. A meta-based recommendation is not the same as a measured head-to-head result.

Match duration: Community-hosted Rone Arena buckets, fetched by rank and lane (6-hour target, 24-hour maximum). These bucket-level statistics are not directly comparable to the ranked-hero win rate without matching match-length scope and observation times.

Patch and collection: A version hint does not verify which patch an individual ranked snapshot covers. Fetch timestamps describe MHQ retrieval, not the timestamp of every match in the upstream sample.

Alerts: Failed ranked and duration refreshes are logged on the server, persisted in the private refresh-alert ledger, and displayed here. An API failure is never replaced by an invented metric.