Changes were made so that the DDoS protection does not get active by a few hundreds of connections to the tracker. I am running about 600 torrents without issues these last days.

Your 503 error / time outs is displayed where, in your browser, or in your torrent client Transmission?

Personally I get often white screens or 502 errors, which disappear after refreshing the page. The Administrators still search for the cause of that to fix it.

Thanks for the info Joker.  However, now I've noticed that twice when I started 113 torrents, I started having error 503, followed by timeouts on all 113 torrents.  I stopped the torrents, and the timeouts continued for 6 hours; I also experience timeouts on the web site.  After six hours, I started getting scrapes from the tracker again; it also took at least 6 hours to be able to access the website again.  This happened twice.  It's my impression that new settings on your DOS software bans me (my IP address) because it interprets starting so many seeding torrents as a DOS attack.  I've been manually starting the torrents, but this is monotonous.  Questions:

1.  Does your DOS software ban IP addresses with the behaviour described above?
2.  If it does, what are the settings ie 20 connections per second or what?  If I know then I could start the torrents faster.  I don't want to get banned
3.  If it does ban as above, could the settings be made more similar to what they were before?  I never had problems before

I am having very similar symptoms and I also have a large number of active seeding torrents (about 50+).

I also end up not being able to connect to the tracker or load the website, presumably because of my IP getting banned (using a different IP works).

hyperfilter is working on it. sorry for any problems due to this

1.  Does your DOS software ban IP addresses with the behaviour described above?
2.  If it does, what are the settings ie 20 connections per second or what?  If I know then I could start the torrents faster.  I don't want to get banned
3.  If it does ban as above, could the settings be made more similar to what they were before?  I never had problems before

503 means our DDOS network was not able to establish a connection to the backend (tracker)

so if you just wait and retry it gonna work. suchs timeouts aren't harmful for the tracking at all

Tracker gave HTTP response code 503 (Service Unavailable)

This seems to be a problem with the tracker, not my computer.  I started seeding 100 torrents.  Is anyone else having this problem?  pinging of 185.30.164.12 times out as well, although I do get a reponse from scraping the tracker.

Then in the window with black background which opens, type "ping tracker.gaytorrent**.ru**" without quotes and hit enter. Note the IP, timeout isn't of interest. Next type "ping tracker.gaytorrent**.tw**" and hit enter again. Note the IP.

If either of the two IPs is the old 85.159.237.127, type "ipconfig /flushdns" in that window. If it says sucess, type again the pings, which if your ISP DNS server got updated should show the new IP 185.30.164.12

If the new IP is shown with the ping's, reboot your PC.

In case only the .ru tracker ping shows the new IP, you could change in your torrent client's torrent properties the tracker from .tw into .ru

I spent hours the other day trying to change my system when the main address changed. I didn't know what was happening and I couldn't log on to find out. A friend who could log in was telling me to try all sorts of things. Nothing worked. Then I logged on a little later and everything was OK again.

The only hiccup I've had this time is that all the .tw tracker torrents (not files) needed to be downloaded again as the tracker seems to be .ru again.

See you on the 'other side'

I have tried rebooting and no joy and I have no idea how to do any of the other suggestions. Perhaps someone could post a step by step guide for the computer illiterate. To be frank it lost me when it spoke of  a coomand prompt.

The batch file doesn't work in Windows 7 64 (at least not for me).

It might be worth adding a note that if users are running Avira or any other anti-virus programme, they made need to disable it before they can patch the hosts file.

Regards,

dances