Current service status and rolling 24-hour availability.
Don't take the chart's word for it. The public snapshot needs no signup — hit it directly and read generated_at and sequence in the response.
curl "https://fanlinewire.com/odds.json"
Machine-readable reference for agents: llms.txt.
FanLine Wire is push-based, not polled. Prices arrive over an AWS AppSync GraphQL WebSocket when FanDuel moves a line — so during live games you get bursts, and when nothing is happening the socket goes silent. Silence means the board is settled, not that the feed is down. Judge health by generated_at advancing and your subscription acks, never by tick count.
The WebSocket row is the live push subscription that carries price moves. The REST row is market discovery — the one-time lookup that maps fixtures to market IDs. The snapshot row is the public demo document above, which is rebuilt continuously from the same subscription. They can fail independently, which is why they are graphed separately.
Each bar is a quarter hour of the rolling 24 hours. A block counts as degraded when the snapshot's generated_at stops advancing inside it, and as an outage when the endpoint stops answering. Short gaps therefore show as one amber bar rather than disappearing into a daily percentage.
There is no independent third-party monitoring behind these numbers — they are our own checks against our own endpoint. Treat the chart as operational signal, not as an audited SLA, and run the curl above whenever the answer matters. Nothing here is a performance guarantee.
If the snapshot answers but the timestamp is stale, or the chart disagrees with what you observe, tell us at hello@fanlinewire.com and include the sequence value you saw. That number pins the exact collector tick and makes the report diagnosable.