Production source and preview state
STAR-BUZZ uses records supplied through the Sportmonks Cricket API v2.0. The production credential and documented live, fixture, relation, detail, pagination, status, multi-innings, and quota behaviors were validated before activation. Development and review environments remain visibly labelled and excluded from indexing.
Refresh and cache timing
While a live collection contains active records and the page is visible, the browser requests a fresh live collection every eight seconds. The server keeps a seven-second live cache to share one provider response across visitors and prevent unnecessary upstream traffic. A successful refresh does not guarantee a changed score because the provider may return the same record during breaks, delays, stumps, or ordinary update cadence.
Source updated and feed retrieved
Source updated means the connected provider supplied an update timestamp. Feed retrieved means STAR-BUZZ records when the server received the response because no provider update timestamp was available. These times are not presented as the time of the last ball.
Status labels
Upcoming, Starting, Live, Break, Delayed, Interrupted, Completed, Abandoned, Cancelled, and Postponed are broad STAR-BUZZ states normalized from provider fields. The original provider note is preserved where useful. We do not force every live-score response into a generic “Live” label.
Missing and degraded records
Missing scores use an em dash, missing venues say “Venue to be confirmed,” and missing result notes fall back to the match state. When the provider is unavailable, the website shows a connection-pending or visibly degraded state. It does not silently substitute fabricated scores.
Corrections
Use the Contact page and choose “Match-data report.” Include the match URL, date, teams, disputed field, and a supporting source. STAR-BUZZ may compare the report with provider data before changing any displayed interpretation.