System Status

ATTENTION NEEDED

DomainStatusLast attemptLast successLast error
SCHEDULEHEALTHY12h ago12h ago—
STARTERSHEALTHY12h ago12h ago—
ODDSDEGRADED4m ago4m ago—
LINEUPSHEALTHY4m ago4m ago—
BULLPENSDEGRADED19m ago18m ago—
ENVIRONMENTHEALTHY4m ago4m ago—
GRADINGHEALTHY14h ago14h ago—
QUICK_ANALYSISDEGRADED
coverage 12/12 games on 2026-09-24
1h ago1h ago—
MARKETSHEALTHY1m ago1m ago—
CFB_MODELHEALTHY24m ago23m ago—
SPLITSHEALTHY4m ago4m ago—
GAME_CONTEXTHEALTHY39m ago39m ago—
EXCHANGESHEALTHY9m ago9m ago—
MODELSHEALTHY13d ago13d ago—
NARRATIVEHEALTHYnevernever—

Job kill watch — last 24h

A run that is still "running" long after it started was killed by the platform at its time limit — it never wrote an error. Grading was dead for two days this way (2026-09-10/11). "Slowest finished" is how close completing runs come to the route's budget (60 seconds, except Quick Analysis and the opportunities cache at 120); anything approaching it is the next one to be killed.

JobRunsKilledLast killedSlowest finishedAvg finished
quick_analysis_refresh9222h ago115.4s73.6s
opportunities_cache_refresh1010never48.5s25.6s
relief_appearance_refresh120never46.7s22.2s
opportunity_snapshot460never39.9s27.9s
hr_radar_cache_refresh1050never38.6s13.8s
game_officials_refresh960never36.5s2.0s
cfb_refresh20never34.6s32.4s
game_status_refresh7180never33.7s2.2s
grading30never31.3s23.7s
postgame_data_refresh120never29.8s6.9s
weather_refresh240never15.1s3.4s
odds_refresh_event240never12.2s7.3s
exchange_odds_refresh60never4.4s3.8s
market_odds_refresh480never4.3s3.4s
lineup_refresh960never3.3s1.1s
odds_refresh_featured480never2.6s1.5s
game_context_refresh20never2.6s2.0s
slate_ingestion10never1.1s1.1s
splits_refresh120never0.3s0.2s
market_settlement240never0.3s0.2s
live_scores_refresh30never0.2s0.2s

Admin session

Manual refresh buttons elsewhere in the app require this once ADMIN_PASSWORD or CRON_SECRET is configured on the server.