How fast we’re moving.

Commit cadence, open work, and CI runtime over the last month and year. All numbers pulled from the source repository — no editorial in between.

What we check, and why

The components above cover the critical path from a club’s WordPress site, through the mobile app, and into the scoring backend. Live checks run from this site’s host and are cached 60 seconds; the two scoring-API rings also report their own database health and the exact app version they’re running. Separately, an uptime probe samples each ring every five minutes and rolls the result into the 24-hour, 7-day, and 30-day percentages (and the 90-day bar) under each ring.

• Snapshot Scoring web — this marketing site. If it’s up, you’re reading this.
• Scoring API · production — the backend the App Store / Play release talks to. Go down and the app falls back to offline mode for up to 14 days. The version tag is whatever production is actually serving right now.
• Scoring API · dev / beta — the backend behind the TestFlight and Play internal builds, usually one release ahead of production. An outage here never touches released clubs; it’s shown so you can see what’s coming next.
• Plugin download — clubs pulling the snapshot-results plugin zip or checking for updates. An outage doesn’t affect already-paired clubs; only install/upgrade.
• OAuth pairing — first-time pairing of a club’s WordPress plugin to the app. If it’s down, already-paired clubs keep working.
• Analytics tracker — self-hosted Matomo used only for site analytics. A tracker outage has zero impact on scoring or publishing.

Engineering pulse

The activity row shows aggregates from the source repo: commits in the last 52 weeks, currently-open issues, currently-open PRs, and total CI minutes burned in the last 30 days. The heatmap is a 52-week × 7-day grid of commit counts, brass-tinted where work happened. None of these numbers reflect production health — that’s the live-checks grid above. They’re here so you can see how the project is being maintained, not whether it’s currently up.

What this page doesn’t show (yet)

Rolling uptime is live: each ring carries 24-hour, 7-day, and 30-day percentages plus a 90-day bar, built from a probe that runs every five minutes. What’s still on the list: a written incident log and a maintenance-window schedule. Until those land, an outage just shows up as a red component above and a dip in the bar. The full picture — live state, versions, and uptime history — is available as JSON at /wp-json/snapshot/v1/status if you’d like to wire it into your own monitoring.

Something broken?

Email support@snapshotscoring.com with the component name and the time you saw it fail. We read every report and the team is small enough that you’ll hear back from someone who can actually do something about it.