Reliability
Every run, on the record
Right now: current. The collector finished a full read within its normal cadence: one run plus the minute between runs. Newest finished read 2026-11-06 19:00 UTC (24 s ago).
FanDuel API is an independent data service operated by FF API Inc. It is not affiliated with, endorsed by or sponsored by FanDuel.
Last 14 days
| Day | Runs | Full | Partial | Failed | Longest gap | Median run |
|---|---|---|---|---|---|---|
| 2026-11-06 | 569 | 22 | 547 | 0 | 4 min | 42 s |
| 2026-11-05 | 29 | 0 | 29 | 0 | 4 min | 164 s |
Longest gap is the longest time between two runs that wrote data. A partial run read some games but not all, for example when a page failed or the run reached its time limit.
How collection stays trustworthy
- One collector at a time. Two workers run the same schedule. The active one holds the collector lease and keeps it from run to run; the other stands by. If the active worker's collector process dies, its next tick a minute later sees the dead run and collects. If the whole worker stops, its lease runs out after 2 minutes and the standby takes over on its next tick: collection resumes within 3 minutes.
- No read is lost. If the database cannot take a read, the raw response is kept on the worker's disk and written later, oldest first, with its original time, even when newer reads have been written since.
- The current line never moves backwards. The current line and price come only from the live collector. A response older than what is already stored, such as a cached copy or a read kept during an outage, goes into the history at its own time and never changes them. While reads kept during an outage are written in after a failover, an answer for a past moment within one read interval of that game (one to thirty minutes, by how soon it starts) can show a state from an adjacent read; the current state, and every moment from the collector's next read of the game on, are always right.
- Near games first. Games about to start and games in play are read most often; games days away less often.
- Honest timestamps. Every response says how fresh it is, and never claims to be newer than the newest read.
Status levels
- Current: the newest finished read is at most 5 minutes old (one run of 4 minutes, plus the minute between runs).
- Delayed: at most 10 minutes old, or the newest read covered under half the games.
- Stale: at most 60 minutes old, or a run is still going past its time limit.
- Down: no read in over 60 minutes, the last three runs failed, or nothing has been read yet.
Current status: status page.