Thanks again!
Best regards.

Let's see:

[faq=24]

which clients we recommend:

[faq=26]

and we do not recommend:

[faq=27]

My personal preferences on my MAC are

1. qBitTorrent after
2. uTorrent

I have torrented some years now, even before I "upgraded" from M$ Windoof to MAC OS X. They both worked flawlessly on both OS - I switched to qBitTorrent again because of the nerve-wracking advertising in uTorrent!

BTW: I'm not affiliated to one of both companies and sadly get no money from them for advertising I'm especially not interested in fighting a "holy war" with any supporter of whichever client you prefer. I just talked about my personal preferences.

Sorry that I can't say anything else to the tracker outing but sh.. happens  :blownose:

But I can help you with a tip which we posted countless times in the forum, in guides …

If the tracker goes offline - LEAVE YOU CLIENT RUNNING!!!

Don't be surprised: there is a real reason behind this tip!

Regularly ( ~ every 30 mins) the tracker connects with the clients and asks them about their traffic since the last contact. A good client keeps these values in memory(!) and reports them to the tracker. Also when the tracker didn't ask for a day - a good client keeps his traffic values (in memory!) and reports them at the next request. Might be a very good client saves these values when shut down (I don't know because i don't shut down my client in case the tracker is offline). But I never lost any transfer values (except for a crash on MY COMPUTER) by tracker-outings.

HTH (hope this helps)

OK, thanks for the explanation, but what would be a good client?
Which one would you indicate? Because mine SEEMS to have not saved those values. I say "seem" because it was only for a few minutes, so, for as much as I keep mu up/down values in my mind, when it comes to GB values, some MB of data cannot be noticed.
Anyway, whic client would you indicate?

Thanks again!

But I can help you with a tip which we posted countless times in the forum, in guides …

If the tracker goes offline - LEAVE YOU CLIENT RUNNING!!!

Don't be surprised: there is a real reason behind this tip!

Regularly ( ~ every 30 mins) the tracker connects with the clients and asks them about their traffic since the last contact. A good client keeps these values in memory(!) and reports them to the tracker. Also when the tracker didn't ask for a day - a good client keeps his traffic values (in memory!) and reports them at the next request. Might be a very good client saves these values when shut down (I don't know because i don't shut down my client in case the tracker is offline). But I never lost any transfer values (except for a crash on MY COMPUTER) by tracker-outings.

HTH (hope this helps)

Whatever the issue was, it seems to have been fixed, at least for now.

Sure thing! This afternoon the server was down and i kept seeding a torrent, even it appearing as a red bar on the client. I'm not sure, but almost, that the amount of data I seeded was not added to my upload credit.
And now, this problem with the tracker!

Hope we get a solution soon.

I can tell you that I was seeding something from around the time this happened, and ~1.3GB upload on my part went unaccounted for on my account. That isn't surprising, since my profile showed me as uploading/downloading 0 torrents, even though I had a few active. I didn't know that when I was seeding, though.

Just to be safe, I've stopped my torrent client for now.

Same here! Glad it's not just me.

This might be because of the server issues from 2 days ago. I'll wait and see if they make an announcement about this. I think it's safe to say the users' torrent clients aren't the issue here.

Sure thing! This afternoon the server was down and i kept seeding a torrent, even it appearing as a red bar on the client. I'm not sure, but almost, that the amount of data I seeded was not added to my upload credit.
And now, this problem with the tracker!

Hope we get a solution soon.

This might be because of the server issues from 2 days ago. I'll wait and see if they make an announcement about this. I think it's safe to say the users' torrent clients aren't the issue here.