Service status and observed uptime
Visit status.datafortennis.com for current checks, measured history and automatically recorded incidents. Sign in and manage your account at console.datafortennis.com.
What the monitors measure
A source can be polling successfully while no match score changes. Conversely, a connected WebSocket can serve stale data if a source stops updating. The page separates these conditions. It does not certify complete tournament coverage, every match lifecycle transition, point enrichment or prediction availability. For supported adapter categories, see the Live WebSocket quickstart.
Timing and history
Checks and page refresh run every minute. Last updated at HH:mm UTC is the latest committed measurement, not the time you opened the page. Components without current measurements for more than five minutes become No data.
The 7-day view uses two-hour intervals, 30 days uses eight-hour intervals and 90 days uses daily intervals. Hover, focus or tap a segment for its UTC bounds, measured status and observed/unknown duration. Gray portions have no measurements and are excluded from observed uptime. A percentage is always qualified by the amount of observed time; it is not a monthly contractual SLA. History begins when monitoring starts, with no synthetic backfill. Under extreme state churn, only the latest 400 transitions per component are returned; omitted older periods remain unknown.
Incidents and recovery
Normal failures and recovery require two consecutive minute checks. Unexpected access, incoherent delivery and unexpected physical closures are recorded without waiting for a second occurrence. Missing observations never count as recovery. Incidents state the measured symptom and subsequent successful checks. They do not automatically infer a network, server or provider cause, or claim that a root cause has been permanently fixed.
A green connection check cannot override source delays or unknown observations. If your client is affected while the page looks healthy, preserve the request ID, UTC time, finite error code and last processed cursor. Never send credentials, connection tickets, payloads containing private data or provider endpoints. The status page shares the website hosting platform; independent external checks and operator alerts continue to monitor failures outside that platform.