Customer status

REST endpoints are covered by bounded smoke checks and customer-key usage evidence tooling. Report persistent 5xx, auth, or quota anomalies with the endpoint and timestamp.

Evidence

Production REST smoke checks are in place with same-key usage evidence for the production database.

Next status step

Betspread support compares reported incidents against smoke output, usage rows, and protected-route error evidence.

Live access is entitlement-gated and monitored manually for early paid launch. Customers should include stream channel, close code, and the first failed timestamp in support requests.

Evidence

Controlled live smoke proved auth, subscribe, update, and non-entitled rejection paths; automated customer status is deferred.

Next status step

Add automated Live freshness and subscription error evidence after the status data source is wired.

Coverage can vary by bookmaker, sport, market type, and source health. Treat stale or missing bookmaker rows as source-specific until support confirms a broader incident.

Evidence

Customer-facing coverage pages use verified launch-scope sources; paid-launch and internal coverage evidence are reviewed manually.

Next status step

Persist source x sport x league x market evidence before expanding the customer-visible coverage matrix.

Account, password reset, and billing lifecycle flows use the dashboard, Stripe, transactional email, and operator-assisted support. Contact support if a billing or email action does not arrive.

Evidence

Resend delivery is technically wired but deliverability hardening remains open; Stripe preflight exists while bounded lifecycle smoke is still being completed.

Next status step

Finish billing lifecycle evidence and email deliverability hardening before broad self-serve launch.