Status
Live operational health: when the data was last published, how the automated jobs are doing, and where CI usage sits against the free-tier budget. This page reads the serving database on every request.
Automated workflows
No workflow runs recorded yet. Runs appear here once the automated jobs report in.
Cron ticks
A heartbeat every time a tick actually reaches the database. While a covered match is live or imminent that is every invocation, so the live tick should read seconds-to-minutes old. Otherwise the ticks answer from a cached window and touch nothing, so an idle row is written at most hourly: outside a match window, expect an age up to an hour, not minutes. Older than that, or never, means cron-job.org is not reaching the route at all.
Live coverage
The live coverage sentinel appears here once it has run during a covered live match.
Stuck live
The stuck-live sentinel appears here once it has run.
Push channels
Both transports carry the same events to the same followers, and only the delivery path differs. An iPhone build whose token never reached the server reads as zero here, which is the one failure that looks identical to a quiet night.
Post-toss gap
The post-toss gap sentinel appears here once it has run.
Provisional results
None. Every result we serve is confirmed by the ball-by-ball archive.
Elo self-review spend
No self-review spend recorded yet.
Push health
Push latency appears here once the live tick has logged a wicket or innings break on a covered live match.
GitHub Actions budget
Actions usage will appear once the daily billing sentinel has run.
Cricket feed budget
Feed usage appears while a covered match is live (the scorecard poller records the plan's calls-today counter).