Same here - seems it's been weeks since any import from Binance.  Last successful add from Binance API was 2018-10-25, then it was a week before that. 

I know Binance can be extremely restrictive on their API pulls, and they do not publish all of their "rules", because they do not want anyone to be able to game the system.  I believe Cointracking is doing a lot and expending effort to try to fix this, as I'm sure they're aware and intent on making customers happy.

As a suggestion to Cointracking, in case the following items weren't thought of:

• Binance's API responses warns you when you're about to break their rules, so when they respond with the "Back off" messages, be sure to back off to prevent the full ban.  For example, if you get 429 responses, that's a warning to slow down.  418 is when you've been auto banned due to ignoring their 429 responses too many times.  When you get the red error shown, that means you've been more "hard banned" by IP, which in my experience means the 429, and 418 errors were ignored, OR a malformed request was sent and the WAF (web application firewall) stepped in and is now blocking requests.
• Throttle yourself in a queue so all your requests are evenly dispersed by entitlement and age, and spread out more IP addresses.
• Favor the customers who pay more.  Unlimited subscribers should be queued first, then Pro.  If needed, go one Ultimate, then one Pro. Increase intervals to always prevent the ban per IP.
• Set age limits where a certain age by entitlement triggers an increase in queue.  For example, a Pro waiting 5 days is bumped up the queue ahead of an Unlimited waiting 2 days, but not ahead of an Unlimited waiting 3 days.
• "Spread out more IP addresses" - I realize IP addresses are not "free" but VPS hosts and proxies to host your API pulls are cheap enough, especially if you have paid subscribers.  As low as $5/month in most places, and that's retail.  I don't know how many you can logistically support from one device, or how long you have to wait between queries, but it'd be worth the calculation, I'd bet.
• I'm pretty sure Binance lowers the "risk profile" of API queries for a given API key if it knows the IP address it's coming from.  If you provisioned said VPS host dynamically out in the cloud, assigned it to a swath of users, and showed the dynamically-assigned IP address on the user's Binance API page, such that we could put that on our API Key page at Binance, it would likely reduce the risk of an IP ban for that specific API key, and that would help you out a lot.  For security reasons, you would want to make sure this was an IP address from a VPS host and not from your data center.  For throttling reasons, you would also probably want to assign, ratio-wise, a set number of Unlimited subscribers together with Pro subscribers so that the Unlimited queuing mentioned above would work out better. Note that each IP address would need to be sticky to the user and stay that way.
• If you haven't already, maybe reaching out to Binance and discussing this issue with them would be a worthy endeavor.  I would think they (the largest fee-based exchange by volume) would appreciate you (the largest fee-based tracker, I think) who helps people make sense of their trades.
• Is there still no way to combine CSV and API - is that due to the way BNB and fees are handled?  I wouldn't mind filling in the gaps every few days myself by importing CSV file... I'm hurting quite a bit recently without my Binance trades.

I still love Cointracking!

(and if anyone needs a 10% link from me, and finds my tips helpful, feel free to use my personal code at https://cointracking.info?ref=C937652 or GBU's at https://gunbotuniversity.com/cointracking)