2026 · week 6 · built 2026-10-14T15:52:53+00:00

Source health

Every source this site depends on, with the moment it was last published, the NFL week it covers, and whether it can be asserted as current today. The threshold that decided each label is shown beside it.

What a label means here

FRESH is inside the window where the data can be stated as current. STALE means it was read fine but is past that window — usable as context, not as today’s state. BROKEN means it could not be read or could not be dated at all, and that is not the same as being fine: a check that did not happen never counts as a check that passed.

The windows are per source type, because the shelf life is not the same: a betting line moves in minutes, an injury report lasts a day, a career stat never expires. They are declared once in freshness.py and this page reads them — it does not keep a second copy.

Which week is it two witnesses, and the disagreement if any

From the schedule6first unplayed game · this is what the site publishes
From Sleeper6api.sleeper.app · 2026-10-14T13:59:15+00:00
AgreementAGREEboth witnesses say the same week
Sources10 / 12fresh · 1 stale · 1 broken

1 broken, 1 stale right now

  • Survivor — BROKEN: out/survivor.json is missing (`python scripts/survivor_build.py`)
  • Research (press) — STALE: last published 1d 3h ago: usable as context, but past the 24.0 h in which NEWS can be asserted as CURRENT

Source by source each row carries the threshold that labelled it

SourceFeedsLabelFreshnessCoversAs ofWindow
Schedulenflverse · games.csvcurrent week, final scores, /prediccionesFRESHCURRENTweek 62026-10-14T15:45:12+00:00168 h
Odds (spread/total)nflverse · games.csv/betting, EV and KellyFRESHCURRENTweek 62026-10-14T15:45:12+00:002 h
Rostersnflverse · roster_2026.parquetwho has an NFL team, IR/PUP/exemptFRESHCURRENTweek 62026-10-14T12:52:12+00:00168 h
Injury reportnflverse · injuries_2026.parquetOUT/DOUBTFUL/QUESTIONABLE designationsFRESHCURRENTweek 62026-10-14T12:50:23+00:0072 h
Depth chartsnflverse · depth_charts_2026.parquetwho holds the job (QB, kicker)FRESHCURRENTweek 62026-10-14T12:51:40+00:00168 h
Weekly player statsnflverse · player_stats_2026.parquetweekly projectionsFRESHCURRENTweek 62026-10-14T14:33:27+00:00216 h
Snap countsnflverse · snap_counts_2026.parquetrole and usageFRESHCURRENTweek 62026-10-13T11:01:32+00:00216 h
Draft boardcompiled from player_stats of seasons < S/fantasy, season-long valueFRESHHISTORICALold BY DESIGN: the walk-forward guarantee forbids reading the season it projects, so this is as current as it can be20262026-08-13T12:00:00+00:00—
Weekly projectionscompiled from player_weeks (stats strictly before the published week)/semanal, /fantasy/lineups, /fantasy/waiversFRESHCURRENTweek 6stats through week 52026-10-14T14:33:27+00:00216 h
Research (press)research/<fecha>.json/research, news marksSTALERECENTlast published 1d 3h ago: usable as context, but past the 24.0 h in which NEWS can be asserted as CURRENT20262026-10-13T12:00:00+00:00168 h
Survivorout/survivor.json (compilado)/survivorBROKENUNKNOWNout/survivor.json is missing (`python scripts/survivor_build.py`)—UNKNOWN—
Published marketsderived from features.parquet + games.csv/bettingFRESHCURRENTweek 62026-10-14T15:45:12+00:002 h

Covers answers a different question from As of: a file refreshed ten minutes ago can still be about last week. A row marked BEHIND has a date no one can fault and coverage that has not advanced — the exact shape of a stale answer that does not look stale.

As of is the date of the data, never the moment it was downloaded: fetching a March file today does not make it from today. For the nflverse files the two coincide on purpose — the download preserves the upstream date, and where the server sends none it is replaced by the date of the commit that last touched the file.

What this page cannot tell you

It dates the data, not the ingestion run. A source can be FRESH because someone refreshed it by hand while the scheduled job is still failing — which is exactly what had been happening here for four weeks. The run history lives in GitHub Actions; this page is the half that the site itself can prove.

It also dates what was published, not what sits on a disk somewhere. Refreshing a source without regenerating the payload does not make the site newer, and saying otherwise is the failure this whole section exists to prevent.