Snapshot Scoring

Status

Status

Is it up?

Live checks against every component that matters to scoring a match. Cached 60 seconds. If something breaks, this page will tell you before your director does.

Degraded performance
2 / 5 components · checked 2026-06-03 13:50:12 UTC

Snapshot Scoring web

Up

This marketing site. If you’re reading this, it’s up.

HTTP 200 · 20 ms

Scoring API

Up

The Django REST backend the mobile app talks to. A response means the service is reachable.

HTTP 404 · 287 ms

Plugin download

Down

The snapshot-results plugin zip + metadata endpoint. This has to be up for a club to install or upgrade.

HTTP 404 · 200 ms

OAuth pairing

Down

The token-exchange endpoint that pairs a club’s WordPress plugin to their mobile app. 4xx on HEAD is expected and means the endpoint is up.

HTTP 404 · 209 ms

Analytics tracker

Down

Self-hosted Matomo tracker used by this site. Used for analytics only; a tracker outage has zero impact on scoring.

HTTP 503 · 231 ms
Dev cadence commit cadence: — · build ●
Engineering pulse

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.

Activity at a glance

500Commits · 52w
1Open issues
0Open PRs
0.0CI hours · 30d

Commit heatmap · last 52 weeks

Want every release tagged on a single timeline? See the releases page.

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. Each probe runs from this site’s host every 60 seconds. “Up” means the component responded with an expected HTTP status in under three seconds.

  • Snapshot Scoring web — this marketing site. If it’s up, you’re reading this.
  • Scoring API — the Django backend the mobile app talks to. Go down and the app falls back to offline mode for up to seven days.
  • 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)

Phase one of live-checks is current-state only — “is it up right now and how fast is it responding.” Historical uptime (daily / 7-day / 30-day SLA percentages, incident log, maintenance window schedule) is coming. The underlying JSON is already available 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.