Started going down about 18:05. Back operational about 18:55.
Betfair Down / Betfair site crash
Do we still get caught for liability from time of Failure or are all Bets offjamesedwards wrote: ↑Sat Oct 03, 2026 7:09 pmStarted going down about 18:05. Back operational about 18:55.
Gemini Response:
An API caching issue in the context of the Betfair Exchange API happens when your application, an intermediate proxy, or Betfair's infrastructure stores and serves stale data (such as outdated odds, old market definitions, or un-refreshed order states) instead of fetching real-time data. Because the Betfair Exchange relies on split-second price movements, caching problems can severely disrupt automated betting scripts and trading bots.
Common Causes and ManifestationsLocal Application Caching: Your custom script or trading bot code inadvertently stores market data (listMarketCatalogue or listMarketBook) in local memory or a database for too long, leading your bot to calculate bets based on old prices.
HTTP Proxy / Gateway Caching: Intermediate network layers or HTTP clients incorrectly cache GET-style or repetitive API responses if proper cache-control headers (no-cache, no-store) are missing from the request configuration.Exchange Stream API vs.
Betting API Misalignment:
If you use the Exchange Stream API (sockets) alongside the standard Betting API (polling listMarketBook), race conditions can make it feel like data is "cached" or lagging if synchronization intervals are set incorrectly.
How to Fix and Prevent Caching IssuesDisable Client-Side Caching:
Ensure your HTTP client explicitly sends headers to bypass caches (e.g., Cache-Control: no-cache and Pragma: no-cache).
Rely on Push Data (Exchange Stream API): For high-frequency live betting, migrate away from polling REST API endpoints and use the Betfair Exchange Stream API via TCP sockets.
This receives delta updates (changes only) in real-time, eliminating stale polling cache loops.
Check version and marketId Handling:
Ensure your application isn't retaining old market definitions when markets close and re-open (such as in-play horse racing or football matches).
Cheersgstar1975 wrote: ↑Tue Oct 13, 2026 11:47 amGemini Response:
An API caching issue in the context of the Betfair Exchange API happens when your application, an intermediate proxy, or Betfair's infrastructure stores and serves stale data (such as outdated odds, old market definitions, or un-refreshed order states) instead of fetching real-time data. Because the Betfair Exchange relies on split-second price movements, caching problems can severely disrupt automated betting scripts and trading bots.
Common Causes and ManifestationsLocal Application Caching: Your custom script or trading bot code inadvertently stores market data (listMarketCatalogue or listMarketBook) in local memory or a database for too long, leading your bot to calculate bets based on old prices.
HTTP Proxy / Gateway Caching: Intermediate network layers or HTTP clients incorrectly cache GET-style or repetitive API responses if proper cache-control headers (no-cache, no-store) are missing from the request configuration.Exchange Stream API vs.
Betting API Misalignment:
If you use the Exchange Stream API (sockets) alongside the standard Betting API (polling listMarketBook), race conditions can make it feel like data is "cached" or lagging if synchronization intervals are set incorrectly.
How to Fix and Prevent Caching IssuesDisable Client-Side Caching:
Ensure your HTTP client explicitly sends headers to bypass caches (e.g., Cache-Control: no-cache and Pragma: no-cache).
Rely on Push Data (Exchange Stream API): For high-frequency live betting, migrate away from polling REST API endpoints and use the Betfair Exchange Stream API via TCP sockets.
This receives delta updates (changes only) in real-time, eliminating stale polling cache loops.
Check version and marketId Handling:
Ensure your application isn't retaining old market definitions when markets close and re-open (such as in-play horse racing or football matches).