Understanding Freshness and Latency: Why 'Updated 41s Ago' Matters

The freshness stamp is a confidence signal

PhotonOdds displays a "● updated 41s ago" timestamp on data panels. That number is not decoration. It is a credibility signal that tells you whether the price on screen is still relevant enough to act on.

When you see a price, you need to know: is this price still being offered right now, or is it stale? The freshness timestamp answers that question. The older the timestamp, the higher the risk that the price has already moved or been pulled entirely. That risk is not theoretical — it is a core part of whether an edge still exists.

What causes the delay

When a price changes at a bookmaker, there is latency before you see it. This has two components:

Collection latency is the time from when a bookmaker publishes a price to when PhotonOdds receives it. PhotonOdds collects from bookmakers either by polling on a schedule (every 5–30 seconds, depending on the book) or by subscribing to a push stream.

Display latency is the time from when PhotonOdds processes the price to when it appears on your screen.

Collection latency is usually the larger piece. The collection method — polling vs. push — directly affects how fresh your prices are.

Polling and push work differently. With polling, you ask for the current price on a schedule — if the schedule is 10 seconds, you might see a price up to 10 seconds old. With push or WebSocket, the server sends updates to you the moment prices change; latency is purely the network round-trip.

Neither approach is universally better. Polling is simpler to deploy at scale but introduces delay. Push is lower latency but requires handling persistent connections. For more on this choice, see Odds API: Webhooks vs. Polling — Which Fits Your Use Case.

What the timestamp tells you

If PhotonOdds says "updated 41 seconds ago," that price was confirmed by the bookmaker 41 seconds before you saw this screen. In that time:

• The price may have moved.
• The limit may have changed.
• The market may have closed.

You cannot know for certain without checking the live price at the bookmaker. But the timestamp tells you the risk profile: a 10-second-old price is more likely to still be there than a 2-minute-old price.

Illustrative freshness scenarios

There is no hard rule like "anything over 30 seconds is unusable." Instead, think about it in context:

• Pre-match football moneyline, 10 seconds old: probably fine. The line is stable pre-match and the 10-second window is short.
• Pre-match football moneyline, 90 seconds old: proceed with caution. The market may have moved; check the current line before betting.
• Live/in-play market, 30 seconds old: stale. In-play markets move quickly. A 30-second-old price could easily be gone or significantly shifted.
• Correct-score market, 2 minutes old: probably stale. Illiquid markets move less predictably and a cached price is risky.

The freshness risk scales with two factors: market volatility (how fast prices typically move) and liquidity (how sensitive the price is to individual bets). Liquid, stable pre-match lines forgive older timestamps better than illiquid in-play markets.

What causes latency

Collection interval

If PhotonOdds polls a bookmaker every 10 seconds, you will see prices that are at most 10 seconds old (plus network and processing delay). Some bookmakers are polled more often, some less often, depending on the cost and value of freshness for that bookmaker.

Pinnacle, the reference bookmaker, is polled more frequently because its prices are sharper. Soft bookmakers may be polled less frequently.

Network latency

Time for a request to travel from PhotonOdds to a bookmaker's servers and back. This varies with geography, network conditions, and traffic.

Processing time

PhotonOdds receives a price, validates it, and stores it. This usually contributes minimally to total latency, but under heavy load can add delay.

Browser delivery

The price then travels from PhotonOdds to your browser. Manual refreshes can introduce further display lag; available delivery methods depend on the product and plan.

How freshness affects your decision-making

Freshness is one of several checks before you act on an alert:

1. Is the alert legitimate? — did it match my rules and sport?
2. Is the price still available? — how fresh is the timestamp?
3. Is the edge still there? — what is the current line, not the one in the alert?
4. Can I physically bet on it? — is my account still available, or have I hit a limit?

An old timestamp does not disqualify an alert. It is a flag that says "verify this before betting." Use The Drop Model framework to read the full market context.

Freshness in the API

If you are building a tool on the Developer Odds API, the API response includes a timestamp for each price. Use it the same way: as a signal of how old the data is. When you fetch an endpoint, check the timestamp in the response. If it is older than your risk tolerance for that market type, discard it or re-fetch.

The /odds endpoint returns current prices. The /odds/history endpoint returns historical prices tagged with their timestamp, letting you study how prices evolved. See API Response Shapes: Odds, Best Price, and History Endpoints Explained for the data structure.

Building confidence in stale data

You cannot eliminate latency — it is a function of how markets operate. But you can:

1. Understand your bookmaker's API update frequency — if you know a bookmaker updates every 30 seconds, you know a price could be up to 30 seconds old.
2. Normalize for market type — set your own mental threshold for staleness per market (e.g., "pre-match moneyline OK to 60 seconds, in-play OK to 10 seconds").
3. Develop a verification habit — before you bet, always check the live price at the bookmaker. The alert and the system are prompts to review, not directions to act.
4. Watch for movement patterns — if you notice prices at a particular book are consistently old, and that affects your decisions, you can shift your alert rules to focus on bookmakers with tighter latency.

Freshness and latency are credibility signals, not problems to solve. They are part of the information you need to make a considered decision. For supported delivery methods and plan details, consult the Odds API page.

18+ only. Betting carries risk. PhotonOdds provides analytical and educational tools, not a promise of profit or a recommendation to place a bet. If gambling is causing harm, see Responsible Gambling.