Status
FighterAPI status and uptime
A probe on GitHub's servers, outside FighterAPI'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.
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
No recent data
HTTP 200, 304 ms, checked 2026-10-19 14:10 UTC
Median 304 ms over 24 hours
No recent data
HTTP 200, 295 ms, checked 2026-10-19 14:10 UTC
Median 295 ms over 24 hours
Uptime
| Surface | 24 hours | 7 days | 90 days |
|---|---|---|---|
| Website | 100% 1 of 15 checks | 100% 1 of 15 checks | 100% 1 of 15 checks |
| MCP server | 100% 1 of 15 checks | 100% 1 of 15 checks | 100% 1 of 15 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
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
| Dataset | Through | Written |
|---|---|---|
| Cards, results and stat sheets | 2026-10-17 | 2026-10-19 10:00 UTC |
| Round-by-round | 2026-10-17 | 2026-10-19 10:01 UTC |
| Cross-check | 2026-10-17 | 2026-10-19 10:01 UTC |
| Ratings | 2026-10-17 | 2026-10-19 10:01 UTC |
| Odds | 2026-10-17 | 2026-10-19 10:01 UTC |
Read from the database. A dataset between seasons holds its last state; see the changelog for the reasons.