Skip to content

Status

FastballAPI status and uptime

A probe on GitHub's servers, outside FastballAPI's own hosting, requests the website and the MCP server about every five minutes and records the result. Every figure below is computed from those records. Nothing here is written by hand. The probe and every run of it are public: github.com/sports-data-hq/status.

Some measurements are missing

Measured since 2026-10-19 14:10 UTC. Windows longer than that history cover only the time measured, and say how many checks they rest on.

Right now

Website

No recent data

HTTP 200, 280 ms, checked 2026-10-19 14:10 UTC

Median 280 ms over 24 hours

MCP server

No recent data

HTTP 200, 291 ms, checked 2026-10-19 14:10 UTC

Median 291 ms over 24 hours

Data freshness

Per dataset, below

Full changelog

Uptime

Surface24 hours7 days90 days
Website
100%
1 of 20 checks
100%
1 of 20 checks
100%
1 of 20 checks
MCP server
100%
1 of 20 checks
100%
1 of 20 checks
100%
1 of 20 checks

A five-minute slot is down if any check in it failed. A slot with no check at all, which happens when GitHub's scheduler runs late or skips, is shown as no data and counts as neither up nor down, so a missed run can neither lift the percentage nor hide an outage.

Last 90 days

Website
90 days agoToday
MCP server
90 days agoToday

Green is 99.9% or better, amber 99% or better, red below that, grey no data. Days are UTC.

Incidents

No incidents recorded since 2026-10-19 14:10 UTC. An incident is two or more failed checks in a row.

Data freshness

DatasetThroughWritten
Games and box scores2026-10-182026-10-19 10:00 UTC
Pitches and plate appearances2026-10-182026-10-19 10:00 UTC
Odds2026-10-182026-10-19 15:05 UTC
Player props—2026-10-19 15:05 UTC
Run values and ratings2026-10-182026-10-19 10:00 UTC

Read from the database. A dataset between seasons holds its last state; see the changelog for the reasons.