How long does the Foundry USA Pool retain historical hashrate data?

Sub-Account Hashrate

Hourly Averages: 30 days
Daily Averages: Forever

Worker Hashrate

Hourly Averages: 3 days
Daily Averages: 90 days

Archive beyond the retention window

You can keep an archive of your own, beyond the retention window above (eg. 30 days for hourly average hashrate).

Option A: Automate with API

Fetch hashrate data on a schedule (cron, cloud function, etc.) and append it to your database/CSV.
Authenticate with your API key via the X-API-KEY header.
Use the appropriate endpoint and parameters.
1. API Endpoint: https://api.foundryusapool.com/subaccount_hashrate_day/{subAccountName}
2. Parameters (eg: ?coin=BTC&startDateUnixMs=…&endDateUnixMs=… (example in KB))
Store the raw results
1. See the API documentation for units, timestamp formats, field definitions, and endpoint-specific responses. Search for “hashrate”, for example.

Suggested refresh cadence:

Scope	Metric	Pool retention	Suggested archive refresh
Sub‑account	Hourly	30 days	Weekly (minimum: every 28–30 days)
Worker	Hourly	3 days	Daily
Worker	Daily	90 days	Monthly
Sub‑account	Daily	Indefinite	Optional (useful for your own single‑store of truth)

Tip: If you only need monthly summaries, sub‑account daily hashrate (retained indefinitely) often suffices and minimizes archiving overhead (source).

Option B: Microsoft Excel

Use our step‑by‑step KB article to connect Excel to the Foundry USA Pool API, then refresh and save snapshots on a cadence: How to use the Foundry USA Pool and API Keys with Microsoft Excel.

Suggested cadence:

Sub‑account hourly: refresh & save at least every 28–30 days (weekly is safer).
Worker hourly: refresh daily (or use Option A to automate).
Worker daily: refresh monthly (before 90 days).