Skip to content
datasportsAPI

Status

The checks are wired. The whistle hasn't gone yet.

Status checks start the minute the API takes live traffic. Until then every component below reads Not yet reporting and the 90-day history is empty. A blank board beats a made-up uptime number.

All systems

Not yet reporting

Monitoring begins with the API. From then on every component is checked once a minute and the result lands here.

Interval
60 s
History
90 days
Clock
UTC
Since
—

Components

  • REST API

    Answers every /v2 request.

    Not yet reporting
    30 days agoNo uptime figure until checks runToday

    Check · An authenticated request to a light endpoint, timed, from inside our own network.

  • WebSocket stream

    Pushes live changes to Business connections.

    Not yet reporting
    30 days agoNo uptime figure until checks runToday

    Check · Mints a ticket, opens a connection and waits for the welcome frame.

  • Live feed

    The incoming stream of scores, clocks and statuses.

    Not yet reporting
    30 days agoNo uptime figure until checks runToday

    Check · Checks how long ago the last live update arrived while matches are in play.

  • Data fetching

    Workers that pull lineups, statistics, events and the rest.

    Not yet reporting
    30 days agoNo uptime figure until checks runToday

    Check · Confirms the workers are running and that recent jobs finished.

  • Media CDN

    Serves team, league and player images.

    Not yet reporting
    30 days agoNo uptime figure until checks runToday

    Check · Fetches a known image from the CDN and checks the response.

  • Database

    Stores fixtures, tables, keys and usage.

    Not yet reporting
    30 days agoNo uptime figure until checks runToday

    Check · A read and a write round trip, timed.

  • Key store

    Looks up API keys and plans on every request.

    Not yet reporting
    30 days agoNo uptime figure until checks runToday

    Check · Resolves a test key and confirms its plan comes back.

KeyNo data(every day so far)OperationalDegradedOutageMaintenance

Incidents

The incident log opens when monitoring starts. Every incident will get a dated write-up here: what broke, what we did and when it was resolved.

What we watch

Seven positions, one formation.

A request crosses the edge, is checked against the key store and answered from the database. Live updates come in through the feed and leave through the stream. When one position falters, this map shows which others feel it.

Edge
REST API · WebSocket stream · Media CDN
Core
Key store · Database
Sources
Data fetching · Live feed