CoinTracker Not Syncing? Why Sync Fails and How to Fix It (2026)

When CoinTracker is not syncing, the cause is almost always a broken connection between your exchange and CoinTracker, not a fault in the software itself. An expired API key, a permissions change, a rate limit, or a CSV that will not import each have a specific fix. This guide sorts the common sync failures and gives you the exact steps to clear each one.

The good news up front: the vast majority of CoinTracker sync problems are connection issues on your account that you can fix in a few minutes. Outages exist, but they are far less common than an expired key or a throttled API.

Disclaimer: This guide is for informational purposes only. Always consult a qualified CPA regarding your specific situation.

First: Rule Out an Exchange or CoinTracker Outage

Before you change anything, confirm the problem is on your account and not a service-wide outage.

• Check CoinTracker’s status page and X (Twitter) account for incident notices
• Check whether the exchange itself is down, since CoinTracker cannot sync from an exchange that is offline
• Try a different browser or an incognito window to rule out a local cache issue

If everything is up but your sync still fails, the problem is on your connection, and the rest of this guide applies.

Problem 1: Expired or Revoked API Keys

This is the single most common sync failure. API keys do not last forever. They expire, get revoked during exchange security events, or stop working when the exchange updates its API.

Fix it in this order:

1. Delete the old connection in CoinTracker. Do not try to edit a broken key. Remove it cleanly.
2. Generate a fresh read-only key on the exchange. Create a brand new API key and grant read access only.
3. Reconnect in CoinTracker. Paste the new key and let it sync from scratch.

Problem 2: Read-Only Key or Permission Scope Issues

Sometimes the key is valid but lacks the right read scope, or the exchange recently changed which permissions an API key needs. The connection looks live but pulls nothing, or pulls only some account types (spot but not margin, for example).

• Confirm the key has read access to all the account types you use on that exchange
• Recreate the key if the exchange changed its API permission structure
• Check whether the exchange requires whitelisting an IP address for API access, which can silently block CoinTracker

Problem 3: Rate Limits and Partial Pulls

If you hit sync repeatedly, the exchange may throttle you, leaving the sync incomplete. And some exchange APIs cap how far back they reach, so older history never imports even when the connection works.

• Wait an hour after repeated syncs and retry once rather than hammering the button
• If older trades are missing after a successful sync, the API likely under-pulled. Our guide on finding and fixing CoinTracker missing transactions covers how to widen the date range or fill the gap

Problem 4: When CSV Is the Better Path

If an exchange API is simply unreliable, or the account is closed, stop fighting the connection and import a file instead.

1. Export your complete transaction history as CSV from the exchange, covering all years
2. Import that CSV into CoinTracker
3. Make sure you do not also have an API connection to the same exchange running, or you will create duplicates

When Sync Is Working but the Numbers Still Look Wrong

If your connections finally sync but the totals or cost basis still look off, the sync was never the real problem. That usually points to tangled history: unmatched transfers, $0 cost basis from a missing source, or DeFi activity that classified inconsistently. More re-syncing will not fix a data-shape problem.

At that point a crypto tax service can reconcile the account, resolve the labeling and cost basis calls, and hand you a report you can file and defend. If your report is a tangle rather than a single broken connection, see our guide on getting human cleanup help for a messy CoinTracker or Koinly report.

Key Takeaways

• Bottom line: “CoinTracker not syncing” is almost always a broken connection on your account, so rule out an outage once, then look at your API keys
• Start with the highest-yield fix: delete the dead connection and reconnect with a fresh read-only key, which clears most sync failures
• Keep keys read-only. CoinTracker never needs trade or withdrawal permission, and unused scopes only add risk
• When the API stays flaky or the account is closed, a full CSV export is the dependable fallback, just never run CSV and API on the same exchange at once
• Decision point: if syncs finally work but the numbers are still wrong, the issue is tangled history, and a crypto tax service can reconcile it before the deadline