Most of my torrents are getting errors when trying to announce.

The majority are getting "A connection attempt failed because the connected party did not properly respond after a period of time...", with a few "The semaphore timeout period has expired" and "timed out", and the rare "An existing connection was forcibly closed by the remote host". Trying the announcement URL in a browser results in "Page didn't respond" errors.

This has been going on for three days now. I have contacted the help desk twice and the first time they admitted they had a "short outage" and that everything should be fine now. It was now. And I haven't heard back from the second attempt as contacting the help desk.

I think their server is overloaded and dropping requests (an attack?), or is having problems and isn't able to respond to all request.

@BKisalive I've been getting "certificate verify failed" errors on all my torrents, starting sometime today. It appears the SSL certificate for their tracker has expired. Hopefully they'll get it fixed soon. I am however still seeding, but cannot start a new download.

Got another reply from the help desk. They say it's either peer blocking software or ISP DNS issues. I don't know about that. It was fine until they had their outage a few days ago, and then it's been like this since. I've tried Google's DNS and no difference.

I'm in Canada. Anyone else?

So, for me, it keeps fluctuating. Right now, around 60% good but falling. The torrents are seeding and uploading just fine. But the other 40%, are getting the error. Funny thing though, a few of the 40% are actually still seeding and are actively uploading to other peers, like the announcement was received but never responded to.

This afternoon, I heard back from the helpdesk, asking what client program I was using and as I replied, I checked the status and noticed that it was over 60% good and was getting better at about 2 to 3 torrents a second. Left it for 5 minutes and it got up to 75% good. Left it for another 30 to 45 minutes and came back and it was down to 35% good and falling at the same rate. An hour ago, it was down to 4%.

Now, after typing this post, it's back to 50% and still falling.

Yup. 502 Bad Gateway. Other torrent trackers working normally. Just gaytor.rent is affected.

@MrMazda FYI: Over the last couple of days, the tracker will start responding to my torrents and I can get to 100% seeding. After about an hour, maybe two, the tracker stops responding for a few hours and I get down to almost 0% again. Couple hours later, it repeats. It has been going up and down consistently. Right now it's in the getting better stage.

Torrents from other sites have no problems and are seeding 100%.

So, for me, it keeps fluctuating. Right now, around 60% good but falling. The torrents are seeding and uploading just fine. But the other 40%, are getting the error. Funny thing though, a few of the 40% are actually still seeding and are actively uploading to other peers, like the announcement was received but never responded to.

This afternoon, I heard back from the helpdesk, asking what client program I was using and as I replied, I checked the status and noticed that it was over 60% good and was getting better at about 2 to 3 torrents a second. Left it for 5 minutes and it got up to 75% good. Left it for another 30 to 45 minutes and came back and it was down to 35% good and falling at the same rate. An hour ago, it was down to 4%.

Now, after typing this post, it's back to 50% and still falling.

Got another reply from the help desk. They say it's either peer blocking software or ISP DNS issues. I don't know about that. It was fine until they had their outage a few days ago, and then it's been like this since. I've tried Google's DNS and no difference.

I'm in Canada. Anyone else?

Most of my torrents are getting errors when trying to announce.

The majority are getting "A connection attempt failed because the connected party did not properly respond after a period of time...", with a few "The semaphore timeout period has expired" and "timed out", and the rare "An existing connection was forcibly closed by the remote host". Trying the announcement URL in a browser results in "Page didn't respond" errors.

This has been going on for three days now. I have contacted the help desk twice and the first time they admitted they had a "short outage" and that everything should be fine now. It was now. And I haven't heard back from the second attempt as contacting the help desk.

I think their server is overloaded and dropping requests (an attack?), or is having problems and isn't able to respond to all request.

Same error for me. Tried to access the tracking in my browser but was Unresponsive.

@BKisalive I've been getting "certificate verify failed" errors on all my torrents, starting sometime today. It appears the SSL certificate for their tracker has expired. Hopefully they'll get it fixed soon. I am however still seeding, but cannot start a new download.

The search isn't working properly. If only one of the 'Where to Search' options, "Torrent Name", "Torrent Description" and "Torrent Filename", is selected, it still searches in all three. There are search results returned that don't have any of the words I am searching for when only "Torrent Name" is selected. In fact, I can deselect all three of these and I get the same number of search results as though selecting only one of the optons. This appears to be on both the new and old design. The "Freeleech Only" and "On Wishlist Only" filters appear to still work.